Christoph Hellwig wrote:
On Tue, Sep 04, 2007 at 09:55:45AM -0700, H. Peter Anvin wrote:
Apparently XEN does not keep the contents of the 48-bit gdt_48 data
structure that is passed to lgdt in the XEN machine state. Instead it
appears to save the _address_ of the 48-bit
On Tue, Sep 04, 2007 at 09:55:45AM -0700, H. Peter Anvin wrote:
>
> Apparently XEN does not keep the contents of the 48-bit gdt_48 data
> structure that is passed to lgdt in the XEN machine state. Instead it
> appears to save the _address_ of the 48-bit descriptor
> somewhere.
Hi Linus,
Please pull:
git://git.kernel.org/pub/scm/linux/kernel/git/hpa/linux-2.6-x86setup.git
for-linus
Christian Ehrhardt (1):
[x86 setup] Work around bug in Xen HVM
arch/i386/boot/pm.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
[Log messages and full diffs
Hi Linus,
Please pull:
git://git.kernel.org/pub/scm/linux/kernel/git/hpa/linux-2.6-x86setup.git
for-linus
Christian Ehrhardt (1):
[x86 setup] Work around bug in Xen HVM
arch/i386/boot/pm.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
[Log messages and full diffs
On Tue, Sep 04, 2007 at 09:55:45AM -0700, H. Peter Anvin wrote:
Apparently XEN does not keep the contents of the 48-bit gdt_48 data
structure that is passed to lgdt in the XEN machine state. Instead it
appears to save the _address_ of the 48-bit descriptor
somewhere.
Christoph Hellwig wrote:
On Tue, Sep 04, 2007 at 09:55:45AM -0700, H. Peter Anvin wrote:
Apparently XEN does not keep the contents of the 48-bit gdt_48 data
structure that is passed to lgdt in the XEN machine state. Instead it
appears to save the _address_ of the 48-bit
6 matches
Mail list logo
