qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Marcel Apfelbaum <marcel.a@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, ehabkost@redhat.com, mst@redhat.com,
	stefanha@redhat.com, armbru@redhat.com, aliguori@amazon.com,
	pbonzini@redhat.com, lersek@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3] tests/qdev-global-props: fixes due to machine conversion to QOM
Date: Tue, 11 Mar 2014 18:11:55 +0100	[thread overview]
Message-ID: <531F43DB.4030405@suse.de> (raw)
In-Reply-To: <1394552156-18901-1-git-send-email-marcel.a@redhat.com>

Hi Marcel,

Am 11.03.2014 16:35, schrieb Marcel Apfelbaum:
> To be applied on top of:
>     hw/boards: converted current_machine to be an instance of MachineClass
> Rebased for qom-next branch of Andrea's QOM tree.
> 
> Patch 1: allows to assign QEMUMachine "automatically",
>          and not only in vl.c (we need this in tests)
> Patch 2: converts "none-machine" to QOM
> Patch 3: Fixes qdev-global-props by adding the "none-machine"
>          to the tree.
> 
> Cc: Andreas Färber <afaerber@suse.de>
> 
> Marcel Apfelbaum (3):
>   hw/machine: move QEMUMachine assignment into the core machine
>   hw/null-machine: Convert null machine to QOM
>   tests/qdev-global-props: Manually add an instance of a QOM machine

It seems I am to blame for most of the problems you are working around
now, so let's not be too shy to correct myself and make things easier on
us. ;)

I'd rather not take the class_base_init patch - for one class_init would
be more correct, but for another I generally don't like putting such
requirements onto use of a base class. The null machine seems indeed low
hanging fruit for further cleanups - but can't we start by making
MachineClass used instead of QEMUMachine? Then we won't need to assign
mc->qemu_machine any more and can start dropping machine_none.

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  parent reply	other threads:[~2014-03-11 17:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11 15:35 [Qemu-devel] [PATCH 0/3] tests/qdev-global-props: fixes due to machine conversion to QOM Marcel Apfelbaum
2014-03-11 15:35 ` [Qemu-devel] [PATCH 1/3] hw/machine: move QEMUMachine assignment into the core machine Marcel Apfelbaum
2014-03-11 15:53   ` Marcel Apfelbaum
2014-03-11 15:35 ` [Qemu-devel] [PATCH 2/3] hw/null-machine: Convert null machine to QOM Marcel Apfelbaum
2014-03-11 15:47   ` Eric Blake
2014-03-11 15:50     ` Marcel Apfelbaum
2014-03-11 15:35 ` [Qemu-devel] [PATCH 3/3] tests/qdev-global-props: Manually add an instance of a QOM machine Marcel Apfelbaum
2014-03-11 17:11 ` Andreas Färber [this message]
2014-03-11 19:44   ` [Qemu-devel] [PATCH 0/3] tests/qdev-global-props: fixes due to machine conversion to QOM Marcel Apfelbaum

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=531F43DB.4030405@suse.de \
    --to=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lersek@redhat.com \
    --cc=marcel.a@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).