All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-block@nongnu.org, mark.cave-ayland@ilande.co.uk,
	qemu-devel@nongnu.org, hpoussin@reactos.org, qemu-ppc@nongnu.org,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH RFC for-2.3? 0/8] prep: Fix pc87312 for -device usage
Date: Mon, 30 Mar 2015 18:42:20 +0200	[thread overview]
Message-ID: <87wq1yfndf.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <551975F3.3080204@redhat.com> (Paolo Bonzini's message of "Mon, 30 Mar 2015 18:12:35 +0200")

Paolo Bonzini <pbonzini@redhat.com> writes:

> On 30/03/2015 16:25, Markus Armbruster wrote:
>> Andreas Färber <afaerber@suse.de> writes:
>> 
>>> Hello Markus et al.,
>>>
>>> This series attempts to fix the -device pc87312 issues you reported.
>>>
>>> I can't add alias properties for devices that don't get created
>>> before realize.
>>> Therefore this involves moving code for various ISA devices, to enable us
>>> to initialize the objects early for alias properties and realizing them
>>> as part of the composite device once the configuration is known, also fixing
>>> error propagation while at it. Probably needs a further iteration.
>>>
>>> Yes, it's terribly invasive, that's why the code was as it is.
>>> But the code movements are quite trivial, as long as no in-air
>>> conflicts occur.
>> 
>> Pity we have to move the state structs to the header, but that what we
>> have to do to make them embeddable.  And I understand embedding is how
>> we do sub-devices ("part of" instead of "plugged into").
>> 
>> Your changes are quite regular.  They don't look scary to me, but that
>> could be just ignorance.  They're non-trivial enough though to make wary
>> of merging them for 2.3 this late.
>
> The question is really: what is gained from this series as of 2.3?  Is
> anything actually using "-device pc87312"?  It was broken before IIUC,
> so it can remain broken for one more version.  Markus's patches would
> just add one more "git revert" to this series, basically.

My series adds four FIXME comments in two commits.  Both commits add
more of them elsewhere.

If my series goes in first, then rebasing this series on top should drop
the four FIXMEs again.

If this series goes first, then I have to rebase minr to drop the four
FIXMEs and replace an example in a commit message.

  parent reply	other threads:[~2015-03-30 16:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-29 17:53 [Qemu-devel] [PATCH RFC for-2.3? 0/8] prep: Fix pc87312 for -device usage Andreas Färber
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 1/8] parallel: Factor out header for ISAParallelState struct Andreas Färber
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 2/8] pc87312: Create isa-parallel in-place and add alias par0-chardev property Andreas Färber
2015-03-30 14:12   ` Markus Armbruster
2015-03-30 14:36     ` Andreas Färber
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 3/8] serial: Move ISASerialState to header Andreas Färber
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 4/8] pc87312: Create UARTs in-place and add alias properties Andreas Färber
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 5/8] fdb: Move FDCtrlISABus to header Andreas Färber
2015-03-31  1:38   ` John Snow
2015-05-19 13:02     ` Andreas Färber
2015-05-19 15:40       ` John Snow
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 6/8] pc87312: Create FDC in-place Andreas Färber
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 7/8] ide: Move ISAIDEState to header Andreas Färber
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 8/8] pc87312: Create IDE in-place Andreas Färber
2015-03-30 14:25 ` [Qemu-devel] [PATCH RFC for-2.3? 0/8] prep: Fix pc87312 for -device usage Markus Armbruster
2015-03-30 16:12   ` Paolo Bonzini
2015-03-30 16:18     ` Andreas Färber
2015-03-30 18:09       ` Markus Armbruster
2015-03-30 16:42     ` Markus Armbruster [this message]
2015-03-30 17:49 ` Andreas Färber

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=87wq1yfndf.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=afaerber@suse.de \
    --cc=hpoussin@reactos.org \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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.