All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH] kvm/x86: enlarge number of possible CPUID leaves
Date: Wed, 01 Dec 2010 14:24:00 +0200	[thread overview]
Message-ID: <4CF63E60.4050309@redhat.com> (raw)
In-Reply-To: <1291202264-3128-1-git-send-email-andre.przywara@amd.com>

On 12/01/2010 01:17 PM, Andre Przywara wrote:
> Currently the number of CPUID leaves KVM handles is limited to 40.
> My desktop machine (AthlonII) already has 35 and future CPUs will
> expand this well beyond the limit. Extend the limit to 80 to make
> room for future processors.
>
> Signed-off-by: Andre Przywara<andre.przywara@amd.com>
> ---
>   arch/x86/include/asm/kvm_host.h |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> Hi,
> I found that either KVM or QEMU (possibly both) are broken in respect
> to handling more CPUID entries than the limit dictates. KVM will
> return -E2BIG, which is the same error as if the user hasn't provided
> enough space to hold all entries. Now QEMU will continue to enlarge
> the allocated memory until it gets into an out-of-memory condition.
> I have tried to fix this with teaching KVM how to deal with a capped
> number of entries (there are some bugs in the current code), but this
> will limit the number of CPUID entries KVM handles, which will surely
> cut of the lastly appended PV leaves.
> A proper fix would be to make this allocation dynamic. Is this a
> feasible way or will this lead to issues or side-effects?
>

Well, there has to be some limit, or userspace can allocate unbounded 
kernel memory.

-- 
error compiling committee.c: too many arguments to function


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH] kvm/x86: enlarge number of possible CPUID leaves
Date: Wed, 01 Dec 2010 14:24:00 +0200	[thread overview]
Message-ID: <4CF63E60.4050309@redhat.com> (raw)
In-Reply-To: <1291202264-3128-1-git-send-email-andre.przywara@amd.com>

On 12/01/2010 01:17 PM, Andre Przywara wrote:
> Currently the number of CPUID leaves KVM handles is limited to 40.
> My desktop machine (AthlonII) already has 35 and future CPUs will
> expand this well beyond the limit. Extend the limit to 80 to make
> room for future processors.
>
> Signed-off-by: Andre Przywara<andre.przywara@amd.com>
> ---
>   arch/x86/include/asm/kvm_host.h |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> Hi,
> I found that either KVM or QEMU (possibly both) are broken in respect
> to handling more CPUID entries than the limit dictates. KVM will
> return -E2BIG, which is the same error as if the user hasn't provided
> enough space to hold all entries. Now QEMU will continue to enlarge
> the allocated memory until it gets into an out-of-memory condition.
> I have tried to fix this with teaching KVM how to deal with a capped
> number of entries (there are some bugs in the current code), but this
> will limit the number of CPUID entries KVM handles, which will surely
> cut of the lastly appended PV leaves.
> A proper fix would be to make this allocation dynamic. Is this a
> feasible way or will this lead to issues or side-effects?
>

Well, there has to be some limit, or userspace can allocate unbounded 
kernel memory.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2010-12-01 12:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 11:17 [PATCH] kvm/x86: enlarge number of possible CPUID leaves Andre Przywara
2010-12-01 11:17 ` [Qemu-devel] " Andre Przywara
2010-12-01 12:24 ` Avi Kivity [this message]
2010-12-01 12:24   ` [Qemu-devel] " Avi Kivity
2010-12-01 12:55   ` Andre Przywara
2010-12-01 12:55     ` [Qemu-devel] " Andre Przywara
2010-12-08 12:14     ` Avi Kivity
2010-12-08 12:14       ` [Qemu-devel] " Avi Kivity
2010-12-08 11:13 ` Andre Przywara
2010-12-08 11:13   ` [Qemu-devel] " Andre Przywara
2010-12-08 12:11   ` Avi Kivity
2010-12-08 12:11     ` [Qemu-devel] " 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=4CF63E60.4050309@redhat.com \
    --to=avi@redhat.com \
    --cc=andre.przywara@amd.com \
    --cc=kvm@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.