From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Isaku Yamahata <yamahata@valinux.co.jp>,
Gerd Hoffmann <kraxel@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCHv2] piix: fix up/down races + document
Date: Sun, 1 Apr 2012 12:06:16 +0300 [thread overview]
Message-ID: <20120401090616.GB22071@redhat.com> (raw)
In-Reply-To: <20120401082618.GA9265@redhat.com>
On Sun, Apr 01, 2012 at 11:26:18AM +0300, Gleb Natapov wrote:
> On Sun, Apr 01, 2012 at 11:22:33AM +0300, Michael S. Tsirkin wrote:
> > > And if pci-hotplug could be done as cpu-hotplug, then it would simplify pci-hotplug
> > > (guest would only need to read PCI_BASE) and probably it would be possible to unify hotplug
> > > code for pci/cpu. But that for sure will break compatibility.
> >
> > Which isn't really acceptable.
> >
> I do not think it should be taken for granted. We should be able to get
> rid of a crud once in a while.
In general, yes. It needs to be well planned several years in
advance though. Something like
http://www.kernel.org/doc/Documentation/feature-removal-schedule.txt
might be a model.
Breaking compatibility would bring very little
gain in this case though, right?
> --
> Gleb.
next prev parent reply other threads:[~2012-04-01 9:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 12:51 [Qemu-devel] [PATCHv2] piix: fix up/down races + document Michael S. Tsirkin
2012-03-29 13:04 ` Gleb Natapov
2012-03-29 13:30 ` Michael S. Tsirkin
2012-03-29 16:53 ` Alex Williamson
2012-03-29 19:38 ` Michael S. Tsirkin
2012-03-29 19:52 ` Alex Williamson
2012-03-30 12:19 ` Michael S. Tsirkin
2012-03-30 16:05 ` Igor Mammedov
2012-04-01 8:22 ` Michael S. Tsirkin
2012-04-01 8:26 ` Gleb Natapov
2012-04-01 9:06 ` Michael S. Tsirkin [this message]
2012-04-01 9:13 ` Gleb Natapov
2012-04-01 9:19 ` Gleb Natapov
2012-04-01 9:24 ` Gleb Natapov
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=20120401090616.GB22071@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=aurelien@aurel32.net \
--cc=gleb@redhat.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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).