qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27
Date: Tue, 27 Jul 2010 15:22:32 +0200	[thread overview]
Message-ID: <4C4EDD98.50609@redhat.com> (raw)
In-Reply-To: <1280189608.4601.237.camel@x201>

On 07/27/10 02:13, Alex Williamson wrote:
> On Mon, 2010-07-26 at 18:28 -0500, Anthony Liguori wrote:
>> On 07/26/2010 05:28 PM, Anthony Liguori wrote:
>>> On 07/26/2010 04:28 PM, Chris Wright wrote:
>>>> Please send in any agenda items you are interested in covering.
>>>
>>> - 0.13 update
>>>   I'll pre-empt the 0.13 question with an answer.  I'm just testing 
>>> the VNC changes and if all goes well, I'll tag tonight.
>>>
>>>   Initial thinking is to keep 0.14 short and target Dec 1st.
>>>
>>> - if danpb can make it, would like to discuss -help output parsing
>>>   summary: help parsing is terrible, but given the fact that 
>>> capabilities is going to take a while to get totally right, would like 
>>> to discuss an interim solution that gives us more flexibility to do 
>>> reasonable things with the help output.
>>
>> - any additional input on probed_raw?
> 
>  - cpu model #s, does anyone know things that would break if we bumped
> the qemu64 model up to 13 (or higher?) and made definitions for
> Conroe/Penryn/Nehalem use more representative model #s?

That was my topic for the call :)

The currenct qemu64 cpu model is a mess, family 6, model 2 is not even a
64 bit processor, plus we enable a bunch of flags that didn't exist in
those processors: pni, popcnt, cx16, sse4a, lm, nx, lahf_lm, svm, abm
(if I got the list right).

Jes

  reply	other threads:[~2010-07-27 13:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 21:28 [Qemu-devel] KVM call agenda for July 27 Chris Wright
2010-07-26 22:28 ` [Qemu-devel] " Anthony Liguori
2010-07-26 23:28   ` Anthony Liguori
2010-07-27  0:13     ` Alex Williamson
2010-07-27 13:22       ` Jes Sorensen [this message]
2010-07-27  7:19     ` Markus Armbruster
2010-07-27 13:00       ` Anthony Liguori
2010-07-27 13:28         ` Kevin Wolf
2010-07-27 15:22           ` Markus Armbruster
2010-07-27 15:28             ` Anthony Liguori
2010-07-27 15:37               ` Daniel P. Berrange
2010-07-27 16:17               ` Avi Kivity
2010-07-27 16:24                 ` Daniel P. Berrange
2010-07-27 16:29                   ` Chris Wright
2010-07-27 16:32                     ` Avi Kivity
2010-07-27 16:36                       ` Chris Wright
2010-07-27 16:42                         ` Avi Kivity
2010-07-27 17:01                           ` Daniel P. Berrange
2010-07-27 17:37                             ` Avi Kivity
2010-07-27 16:42                     ` Daniel P. Berrange
2010-07-27 16:47                       ` Avi Kivity
2010-07-27 16:48                         ` Avi Kivity
2010-07-28 11:22               ` Markus Armbruster
2010-07-28 11:25                 ` Kevin Wolf
2010-07-28 13:08                   ` Markus Armbruster
2010-07-27 11:51   ` Daniel P. Berrange
2010-07-27 13:30     ` Anthony Liguori
2010-07-27 13:43       ` Cole Robinson

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=4C4EDD98.50609@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=chrisw@redhat.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 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).