search for: shaohui

...guidance here? Should we really add all memory to the > firmware memmap, even if this contradicts with the existing > documentation? (especially, if the actual firmware memmap will *not* > contain that memory after a reboot) For some reason that patch is misattributed - it was authored by Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in a decade. I looked through the email discussion from that time and I'm not seeing anything useful. But I wasn't able to locate Dave Hansen's review comments.

...guidance here? Should we really add all memory to the > firmware memmap, even if this contradicts with the existing > documentation? (especially, if the actual firmware memmap will *not* > contain that memory after a reboot) For some reason that patch is misattributed - it was authored by Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in a decade. I looked through the email discussion from that time and I'm not seeing anything useful. But I wasn't able to locate Dave Hansen's review comments.

hi, my friends: Currently, i am studying the way of hypercall's implementation. i have already known the flow of hypercall's execuation, and i decided to add a new hypercall into the Xen. first, i want to know the detail of one hypercall function, for example, "do_xen_version", but i can not find the location of definition of "do_xen_version". who can help me? i have

...t; >> firmware memmap, even if this contradicts with the existing > >> documentation? (especially, if the actual firmware memmap will *not* > >> contain that memory after a reboot) > > > > For some reason that patch is misattributed - it was authored by > > Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in > > a decade. I looked through the email discussion from that time and I'm > > not seeing anything useful. But I wasn't able to locate Dave Hansen's > > review comments. > > Okay, thank...

...t; >> firmware memmap, even if this contradicts with the existing > >> documentation? (especially, if the actual firmware memmap will *not* > >> contain that memory after a reboot) > > > > For some reason that patch is misattributed - it was authored by > > Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in > > a decade. I looked through the email discussion from that time and I'm > > not seeing anything useful. But I wasn't able to locate Dave Hansen's > > review comments. > > Okay, thank...

...s contradicts with the existing > >>>> documentation? (especially, if the actual firmware memmap will *not* > >>>> contain that memory after a reboot) > >>> > >>> For some reason that patch is misattributed - it was authored by > >>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in > >>> a decade. I looked through the email discussion from that time and I'm > >>> not seeing anything useful. But I wasn't able to locate Dave Hansen's > >>> review comment...

...s contradicts with the existing > >>>> documentation? (especially, if the actual firmware memmap will *not* > >>>> contain that memory after a reboot) > >>> > >>> For some reason that patch is misattributed - it was authored by > >>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in > >>> a decade. I looked through the email discussion from that time and I'm > >>> not seeing anything useful. But I wasn't able to locate Dave Hansen's > >>> review comment...

...;>>>>>> documentation? (especially, if the actual firmware memmap will *not* >>>>>>> contain that memory after a reboot) >>>>>> >>>>>> For some reason that patch is misattributed - it was authored by >>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>>>>> a decade. I looked through the email discussion from that time and I'm >>>>>> not seeing anything useful. But I wasn't able to locate Dave Hansen's >>>>&g...

...;>>>>>> documentation? (especially, if the actual firmware memmap will *not* >>>>>>> contain that memory after a reboot) >>>>>> >>>>>> For some reason that patch is misattributed - it was authored by >>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>>>>> a decade. I looked through the email discussion from that time and I'm >>>>>> not seeing anything useful. But I wasn't able to locate Dave Hansen's >>>>&g...

.... My 11160 is your 11159, and my 11161 is your 11160. Attached please see those patches, Thanks, Winston, -----Original Message----- From: Steven Smith [mailto:sos22@hermes.cam.ac.uk] On Behalf Of Steven Smith Sent: Wednesday, October 11, 2006 10:33 AM To: Wang, Winston L Cc: Stefan Berger; Zheng, Shaohui; xen-devel@lists.xensource.com; sos22@srcf.ucam.org Subject: Re: [Xen-devel] W2K3 Server Installation fails with ACPI=1 on > Sorry to hear more ACPI Windows problem. > > Noticed your issue is W2K3 not W2K: > > W2k3 Server installation issue is caused by HLT instruction; Xin will &...

...ally add all memory to the >> firmware memmap, even if this contradicts with the existing >> documentation? (especially, if the actual firmware memmap will *not* >> contain that memory after a reboot) > > For some reason that patch is misattributed - it was authored by > Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in > a decade. I looked through the email discussion from that time and I'm > not seeing anything useful. But I wasn't able to locate Dave Hansen's > review comments. Okay, thanks for checking. I think...

...ntation? (especially, if the actual firmware memmap will *not* >>>>>>>>> contain that memory after a reboot) >>>>>>>> >>>>>>>> For some reason that patch is misattributed - it was authored by >>>>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>>>>>>> a decade. I looked through the email discussion from that time and I'm >>>>>>>> not seeing anything useful. But I wasn't able to locate Dave Hansen's &g...

...ntation? (especially, if the actual firmware memmap will *not* >>>>>>>>> contain that memory after a reboot) >>>>>>>> >>>>>>>> For some reason that patch is misattributed - it was authored by >>>>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>>>>>>> a decade. I looked through the email discussion from that time and I'm >>>>>>>> not seeing anything useful. But I wasn't able to locate Dave Hansen's &g...

...mware memmap, even if this contradicts with the existing >>>> documentation? (especially, if the actual firmware memmap will *not* >>>> contain that memory after a reboot) >>> >>> For some reason that patch is misattributed - it was authored by >>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>> a decade. I looked through the email discussion from that time and I'm >>> not seeing anything useful. But I wasn't able to locate Dave Hansen's >>> review comments. >> &gt...

...ith the existing >>>>>> documentation? (especially, if the actual firmware memmap will *not* >>>>>> contain that memory after a reboot) >>>>> >>>>> For some reason that patch is misattributed - it was authored by >>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>>>> a decade. I looked through the email discussion from that time and I'm >>>>> not seeing anything useful. But I wasn't able to locate Dave Hansen's >>>>> revie...

...ual firmware memmap will *not* >>>>>>>>>>> contain that memory after a reboot) >>>>>>>>>> >>>>>>>>>> For some reason that patch is misattributed - it was authored by >>>>>>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>>>>>>>>> a decade. I looked through the email discussion from that time and I'm >>>>>>>>>> not seeing anything useful. But I wasn't able to locate Dave...

...ual firmware memmap will *not* >>>>>>>>>>> contain that memory after a reboot) >>>>>>>>>> >>>>>>>>>> For some reason that patch is misattributed - it was authored by >>>>>>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>>>>>>>>> a decade. I looked through the email discussion from that time and I'm >>>>>>>>>> not seeing anything useful. But I wasn't able to locate Dave...

...;> documentation? (especially, if the actual firmware memmap will *not* > >>>>>>> contain that memory after a reboot) > >>>>>> > >>>>>> For some reason that patch is misattributed - it was authored by > >>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in > >>>>>> a decade. I looked through the email discussion from that time and I'm > >>>>>> not seeing anything useful. But I wasn't able to locate Dave Hansen's > &gt...

....cgi?id=1719 X2APIC (1 bug) 1. Fail to bootup sandy bridge under PAE with x2apic enabled (Intel) http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1718 Windows (1 bug) 1. All windows UP guest boot fail http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1704 (Intel) Thanks & Regards, Shaohui _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

..., if the actual firmware memmap will *not* > >>>>>>>>> contain that memory after a reboot) > >>>>>>>> > >>>>>>>> For some reason that patch is misattributed - it was authored by > >>>>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in > >>>>>>>> a decade. I looked through the email discussion from that time and I'm > >>>>>>>> not seeing anything useful. But I wasn't able to locate Dave Hanse...