From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Joerg Roedel <joerg.roedel-5C7GfCeVMHo@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH 0/4 try #2] Fix PAE guests on KVM 32 bit host
Date: Thu, 31 Jan 2008 18:16:28 +0200 [thread overview]
Message-ID: <47A1F45C.5010200@qumranet.com> (raw)
In-Reply-To: <1201787860-20159-1-git-send-email-joerg.roedel-5C7GfCeVMHo@public.gmane.org>
Joerg Roedel wrote:
> This series of patches fixes a boot problem with PAE guests on a 32 bit
> KVM host. These guests try to access the EFER register when running on AMD, get
> an GP and crashing very soon in the boot process. These patches fix that. They
> were tested with 32 bit legacy and PAE Linux and Vista 32 bit.
>
Applied this (decapitalising EFER_RESERVED_BITS, ugh), thanks. I still
expect problems from the EFER-less processors, we'll have to watch out
for them.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-01-31 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 13:57 [PATCH 0/4 try #2] Fix PAE guests on KVM 32 bit host Joerg Roedel
[not found] ` <1201787860-20159-1-git-send-email-joerg.roedel-5C7GfCeVMHo@public.gmane.org>
2008-01-31 13:57 ` [PATCH 1/4] X86: make EFER_RESERVED_BITS configurable for architecture code Joerg Roedel
2008-01-31 13:57 ` [PATCH 2/4] X86: align valid EFER bits with the features of the host system Joerg Roedel
2008-01-31 13:57 ` [PATCH 3/4] VMX: unifdef the EFER specific code Joerg Roedel
2008-01-31 13:57 ` [PATCH 4/4] X86: allow access to EFER in 32bit KVM Joerg Roedel
2008-01-31 16:16 ` Avi Kivity [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47A1F45C.5010200@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=joerg.roedel-5C7GfCeVMHo@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox