From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Avi Kivity <avi@qumranet.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, kvm-devel@lists.sourceforge.net
Subject: Re: [GIT PULL][RESEND #2] KVM Updates for 2.6.23-rc1
Date: Tue, 17 Jul 2007 21:39:05 +0300 [thread overview]
Message-ID: <200707172139.09131.caglar@pardus.org.tr> (raw)
In-Reply-To: <11846910642166-git-send-email-avi@qumranet.com>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
Hi;
17 Tem 2007 Sal tarihinde, Avi Kivity şunları yazmıştı:
> I fixed the issue with the previous patchset. Please provide further
> feedback, or pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git for-linus
>
> This contains kvm updates for the 2.6.23 merge window, including
>
> - performance improvements
> - suspend/resume fixes
> - guest smp
> - random fixes and cleanups
I have a tiny question triggered in my mind after seeing following, sorry if
this was disccussed before;
config KVM
tristate "Kernel-based Virtual Machine (KVM) support"
depends on X86 && EXPERIMENTAL
depends on X86_CMPXCHG64 || 64BIT
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?
Is this intentional or this is here because of an assumption like "processors
supports virtualization already provides PAE", could you please enlighten me?
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-17 18:40 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 [this message]
2007-07-17 19:05 ` H. Peter Anvin
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=200707172139.09131.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=avi@qumranet.com \
--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