All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Benoît Canet" <benoit.canet@irqsave.net>
To: qemu-devel@nongnu.org
Cc: imammedo@redhat.com, ehabkost@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH] forward cpuid leaves when using -cpu host
Date: Mon, 2 Sep 2013 14:45:48 +0200	[thread overview]
Message-ID: <20130902124548.GF5073@irqsave.net> (raw)
In-Reply-To: <1377635906-17274-1-git-send-email-benoit@irqsave.net>


Ping,

I am aware that this patch must be a QObject/CPUState monstruosity but I don't
see how I could store the fact that the cpu derive from a "host" type cpu.
The alternative would be to remember a variable number of leaves and serving
them to the guest as needed but I don't find that much cleaner.

Best regards

Benoît

> Le Tuesday 27 Aug 2013 à 22:38:25 (+0200), Benoît Canet a écrit :
> This patch uses directly cpuid_host to forward the informations instead of
> storing a variable number of leaves in the cpu states.
> 
> Benoît Canet (1):
>   i386: forward CPUID cache leaves when -cpu host is used
> 
>  target-i386/cpu.c |   19 +++++++++++++++++++
>  target-i386/cpu.h |    1 +
>  2 files changed, 20 insertions(+)
> 
> -- 
> 1.7.10.4
> 

  parent reply	other threads:[~2013-09-02 12:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27 20:38 [Qemu-devel] [PATCH] forward cpuid leaves when using -cpu host Benoît Canet
2013-08-27 20:38 ` [Qemu-devel] [PATCH] i386: forward CPUID cache leaves when -cpu host is used Benoît Canet
2013-09-02 12:55   ` Andreas Färber
2013-09-02 12:55     ` Andreas Färber
2013-09-02 13:09     ` Eduardo Habkost
2013-09-02 13:09       ` Eduardo Habkost
2013-09-02 12:45 ` Benoît Canet [this message]
2013-09-02 12:58   ` [Qemu-devel] [PATCH] forward cpuid leaves when using -cpu host Eduardo Habkost

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=20130902124548.GF5073@irqsave.net \
    --to=benoit.canet@irqsave.net \
    --cc=afaerber@suse.de \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --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.