summaryrefslogtreecommitdiff
path: root/service_solahart_jakarta_selatan__082122541663/mach_shadow_objects.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'service_solahart_jakarta_selatan__082122541663/mach_shadow_objects.mdwn')
-rw-r--r--service_solahart_jakarta_selatan__082122541663/mach_shadow_objects.mdwn24
1 files changed, 24 insertions, 0 deletions
diff --git a/service_solahart_jakarta_selatan__082122541663/mach_shadow_objects.mdwn b/service_solahart_jakarta_selatan__082122541663/mach_shadow_objects.mdwn
new file mode 100644
index 00000000..0669041a
--- /dev/null
+++ b/service_solahart_jakarta_selatan__082122541663/mach_shadow_objects.mdwn
@@ -0,0 +1,24 @@
+[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]]
+
+[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
+id="license" text="Permission is granted to copy, distribute and/or modify this
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+[[!tag open_issue_gnumach]]
+
+See also [[gnumach_vm_map_entry_forward_merging]].
+
+
+# IRC, freenode, #hurd, 2012-11-16
+
+ <mcsim> hi. do I understand correct that following is true: vm_object_t a;
+ a->shadow->copy == a;?
+ <braunr> mcsim: not completely sure, but i'd say no
+ <braunr> but mach terminology isn't always firm, so possible
+ <braunr> mcsim: apparently you're right, although be careful that it may
+ not be the case *all* the time
+ <braunr> there may be inconsistent states