From: Kevin Wolf <kwolf@suse.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] MTRR support on x86, part 2
Date: Thu, 29 Jan 2009 18:27:07 +0100 [thread overview]
Message-ID: <4981E6EB.8020203@suse.de> (raw)
In-Reply-To: <4981E12E.3030100@us.ibm.com>
Anthony Liguori schrieb:
> Carl-Daniel Hailfinger wrote:
>> Load and save MTRR state together with machine state.
>>
>> Add support for the MTRRcap MSR which is used by the latest Bochs BIOS
>> and some operating systems.
>>
>> Fix a typo in ext2_feature_name.
>>
>> With this patch, MTRR emulation should be good enough to not trigger any
>> sanity checks in well behaved BIOS/kernel code.
>> Some corner cases for BIOS/firmware usage remain to be implemented, but
>> that can be deferred to another patch.
>> Also, MTRR accesses on hardware not supporting MTRRs should cause #GP.
>> That can be enforced by another patch as well.
>>
>> Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
>>
>> Index: target-i386/helper.c
>> ===================================================================
>> --- target-i386/helper.c (Revision 6461)
>> +++ target-i386/helper.c (Arbeitskopie)
>> @@ -55,7 +55,7 @@
>> };
>> static const char *ext2_feature_name[] = {
>> "fpu", "vme", "de", "pse", "tsc", "msr", "pae", "mce",
>> - "cx8" /* AMD CMPXCHG8B */, "apic", NULL, "syscall", "mttr",
>> "pge", "mca", "cmov",
>> + "cx8" /* AMD CMPXCHG8B */, "apic", NULL, "syscall", "mtrr",
>> "pge", "mca", "cmov",
>>
>
> As best as I can tell, there is no change here. I removed it from the
> diff and applied the rest.
The change seems to be s/mttr/mtrr/
Kevin
next prev parent reply other threads:[~2009-01-29 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 23:41 [Qemu-devel] [PATCH] MTRR support on x86, part 2 Carl-Daniel Hailfinger
2009-01-29 17:02 ` Anthony Liguori
2009-01-29 17:27 ` Kevin Wolf [this message]
2009-01-29 17:37 ` Jung-uk Kim
2009-01-29 19:43 ` Anthony Liguori
2009-01-29 19:32 ` Carl-Daniel Hailfinger
2009-01-29 19:48 ` Anthony Liguori
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=4981E6EB.8020203@suse.de \
--to=kwolf@suse.de \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).