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: qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	Kevin O'Connor <kevin@koconnor.net>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.8 0/2] pc: remove redundant fw_cfg file "etc/boot-cpus"
Date: Tue, 15 Nov 2016 12:07:58 +0100	[thread overview]
Message-ID: <20161115120758.08e26811@nial.brq.redhat.com> (raw)
In-Reply-To: <20161114224401-mutt-send-email-mst@kernel.org>

On Mon, 14 Nov 2016 22:46:14 +0200
"Michael S. Tsirkin" <mst@redhat.com> wrote:

> On Fri, Nov 11, 2016 at 04:21:10PM +0100, Igor Mammedov wrote:
> > 
> > Commit 080ac219cc7d9c55adf925c3545b7450055ad625
> >    pc: Add 'etc/boot-cpus' fw_cfg file for machine with more than 255 CPUs
> > 
> > added "etc/boot-cpus" fw_cfg file durung 2.8 merge window, however
> > QEMU alredy had similar legacy FW_CFG_NB_CPUS fw_cfg entry that
> > should do practically the same. Considering FW_CFG_NB_CPUS's been
> > around for a long time and is used by external projects (firmwares)
> > we can't replace it with 'etc/boot-cpus' fw_cfg file.
> > 
> > Drop redundant 'etc/boot-cpus' fw_cfg file  and reuse FW_CFG_NB_CPUS
> > instead.
> > 
> > So here goes QEMU part of fixup  
> 
> I agree we shouldn't commit to a bad host/guest API
> but I think we need to format it differently.
> First revert the boot-cpus patch for 2.8.
> On top of that, add a patch fixing FW_CFG_NB_CPUS.
Sure, I'll respin.

> 
> 
> > CC: Eduardo Habkost <ehabkost@redhat.com>
> > CC: mst@redhat.com
> > CC: Stefan Hajnoczi <stefanha@gmail.com>
> > CC: "Kevin O'Connor" <kevin@koconnor.net>
> > CC: Gerd Hoffmann <kraxel@redhat.com>
> > CC: Laszlo Ersek <lersek@redhat.com>
> > 
> > Igor Mammedov (2):
> >   fw_cfg: move FW_CFG_NB_CPUS out of fw_cfg_init1()
> >   pc: drop "etc/boot-cpus" fw_cfg file and use FW_CFG_NB_CPUS instead
> > 
> >  include/hw/i386/pc.h  |  4 ++--
> >  hw/arm/virt.c         |  4 +++-
> >  hw/i386/pc.c          | 20 ++++++++------------
> >  hw/nvram/fw_cfg.c     |  1 -
> >  hw/ppc/mac_newworld.c |  1 +
> >  hw/ppc/mac_oldworld.c |  1 +
> >  hw/sparc/sun4m.c      |  1 +
> >  hw/sparc64/sun4u.c    |  1 +
> >  8 files changed, 17 insertions(+), 16 deletions(-)
> > 
> > -- 
> > 2.7.4  

      parent reply	other threads:[~2016-11-15 11:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 15:21 [Qemu-devel] [PATCH for-2.8 0/2] pc: remove redundant fw_cfg file "etc/boot-cpus" Igor Mammedov
2016-11-11 15:21 ` [Qemu-devel] [PATCH for-2.8 1/2] fw_cfg: move FW_CFG_NB_CPUS out of fw_cfg_init1() Igor Mammedov
2016-11-11 15:21 ` [Qemu-devel] [PATCH for-2.8 2/2] pc: drop "etc/boot-cpus" fw_cfg file and use FW_CFG_NB_CPUS instead Igor Mammedov
2016-11-14 15:40 ` [Qemu-devel] [PATCH for-2.8 0/2] pc: remove redundant fw_cfg file "etc/boot-cpus" Stefan Hajnoczi
2016-11-14 20:46 ` Michael S. Tsirkin
2016-11-15 10:23   ` Gerd Hoffmann
2016-11-15 11:07   ` Igor Mammedov [this message]

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=20161115120758.08e26811@nial.brq.redhat.com \
    --to=imammedo@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).