qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	marcel@redhat.com, longpeng2@huawei.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] pc: fix regression introduced by adding 2.8 machine
Date: Fri, 16 Sep 2016 10:03:12 +0200	[thread overview]
Message-ID: <20160916100312.306d34e9@nial.brq.redhat.com> (raw)
In-Reply-To: <20160915181807-mutt-send-email-mst@kernel.org>

On Thu, 15 Sep 2016 18:18:46 +0300
"Michael S. Tsirkin" <mst@redhat.com> wrote:

> On Thu, Sep 15, 2016 at 11:19:09AM -0300, Eduardo Habkost wrote:
> > On Wed, Sep 14, 2016 at 12:01:49PM +0200, Igor Mammedov wrote:  
> > > commit (a4d3c834 pc: Add 2.8 machine) didn't ammend
> > > PC_COMPAT_2_6 to include PC_COMPAT_2_7 which results in
> > > 
> > >     {\
> > >         .driver   = "virtio-pci",\
> > >         .property = "page-per-vq",\
> > >         .value    = "on",\
> > >     },
> > > 
> > > and
> > > 
> > >     {\
> > >         .driver   = TYPE_X86_CPU,\
> > >         .property = "l3-cache",\
> > >         .value    = "off",\
> > >     },
> > > 
> > > being ignored and as result change PC_COMPAT_2_6 behaviour.
> > >   
> > [...]  
> > >  #define PC_COMPAT_2_6 \
> > > +    PC_COMPAT_2_7 \
> > >      HW_COMPAT_2_6 \
> > >      {\
> > >          .driver   = "fw_cfg_io",\  
> > 
> > Isn't this supposed to be unnecessary since commit bacc344c
> > ("machine: add properties to compat_props incrementaly")?
> > 
> > -- 
> > Eduardo  
> 
> 
> Indeed, I tested page-per-vq and it seems on for 2.6.
> Igor, Marcel, could you comment pls?

You are right, I think inconsistency in

#define PC_COMPAT_2_5 \                                                          
    PC_COMPAT_2_6 \                                                              
    HW_COMPAT_2_5  
 
and

#define PC_COMPAT_2_7 \                                                          
    PC_COMPAT_2_8 \                                                              
    HW_COMPAT_2_7

made me think that we still need it.

I'd better clean-up PC_COMPAT_2_5 and PC_COMPAT_2_7

  reply	other threads:[~2016-09-16  8:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 10:01 [Qemu-devel] [PATCH 0/2] pc: fixes broken compat logic Igor Mammedov
2016-09-14 10:01 ` [Qemu-devel] [PATCH 1/2] pc: fix regression introduced by adding 2.8 machine Igor Mammedov
2016-09-14 11:32   ` Marcel Apfelbaum
2016-09-15 14:19   ` Eduardo Habkost
2016-09-15 15:18     ` Michael S. Tsirkin
2016-09-16  8:03       ` Igor Mammedov [this message]
2016-09-14 10:01 ` [Qemu-devel] [PATCH 2/2] target-i386: turn off CPU.l3-cache only for 2.7 and older machine types Igor Mammedov
2016-09-14 11:35   ` Marcel Apfelbaum
2016-09-15 14:23   ` Eduardo Habkost
2016-09-16  8:08     ` Igor Mammedov
2016-09-16 11:31       ` Eduardo Habkost
2016-09-18  0:28 ` [Qemu-devel] [PATCH 0/2] pc: fixes broken compat logic Longpeng (Mike)

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=20160916100312.306d34e9@nial.brq.redhat.com \
    --to=imammedo@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=longpeng2@huawei.com \
    --cc=marcel@redhat.com \
    --cc=mst@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 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).