From: "H. Peter Anvin" <hpa@zytor.com>
To: caglar@pardus.org.tr
Cc: Avi Kivity <avi@qumranet.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, kvm-devel@lists.sourceforge.net,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [GIT PULL][RESEND #2] KVM Updates for 2.6.23-rc1
Date: Tue, 17 Jul 2007 12:05:59 -0700 [thread overview]
Message-ID: <469D1317.1050202@zytor.com> (raw)
In-Reply-To: <200707172139.09131.caglar@pardus.org.tr>
S.Çağlar Onur wrote:
>
> If i'm not wrong X86_CMPXCHG64 depends on CONFIG_X86_PAE which depends on
> HIGHMEM64 and again if i'm not wrong this means distributions who wants to
> provide KVM must enable CONFIG_X86_PAE and CONFIG_HIGHMEM64G from now on?
>
X86_PAE should depend on X86_CMPXCHG64, not the other way around.
I asked Andi Kleen about this on IRC, and he said:
<freitag> the reason was that i didn't want to hack everybody's magic
MSRs into the old verify_cpu.S
verify_cpu.S is dead on i386 (replaced by arch/i386/boot/cpucheck.c)
which does have the flags enable MSR tweaks; it is still being used for
APs on x86-64. However, in the meantime it should be safe to remove
this dependency from i386.
-hpa
next prev parent reply other threads:[~2007-07-17 19:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 16:51 [GIT PULL][RESEND #2] KVM Updates for 2.6.23-rc1 Avi Kivity
2007-07-17 18:39 ` S.Çağlar Onur
2007-07-17 19:05 ` H. Peter Anvin [this message]
2007-07-17 19:15 ` Linus Torvalds
2007-07-17 19:26 ` H. Peter Anvin
2007-07-17 23:25 ` S.Çağlar Onur
2007-07-17 23:38 ` [kvm-devel] " Anthony Liguori
2007-07-17 23:40 ` S.Çağlar Onur
2007-07-18 9:31 ` S.Çağlar Onur
2007-07-18 9:35 ` Avi Kivity
2007-07-18 10:09 ` S.Çağlar Onur
2007-07-18 10:17 ` S.Çağlar Onur
2007-07-18 10:31 ` Avi Kivity
2007-07-18 10:50 ` S.Çağlar Onur
2007-07-20 5:31 ` Avi Kivity
2007-07-20 11:37 ` S.Çağlar Onur
2007-07-18 17:46 ` S.Çağlar Onur
2007-07-18 18:04 ` Avi Kivity
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=469D1317.1050202@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--cc=avi@qumranet.com \
--cc=caglar@pardus.org.tr \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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