From: John Snow <jsnow@redhat.com>
To: Anthony PERARD <anthony.perard@citrix.com>, qemu-devel@nongnu.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
qemu-block@nongnu.org, Paul Durrant <paul@xen.org>
Subject: Re: [PATCH v2] xen: rework pci_piix3_xen_ide_unplug
Date: Tue, 27 Oct 2020 13:33:32 -0400 [thread overview]
Message-ID: <e7d2fef8-a697-398e-4b3b-bf247aac01a5@redhat.com> (raw)
In-Reply-To: <20201027154058.495112-1-anthony.perard@citrix.com>
On 10/27/20 11:40 AM, Anthony PERARD wrote:
> From: Anthony PERARD <anthony.perard@citrix.com>
>
> This is to allow IDE disks to be unplugged when adding to QEMU via:
> -drive file=/root/disk_file,if=none,id=ide-disk0,format=raw
> -device ide-hd,drive=ide-disk0,bus=ide.0,unit=0
>
> as the current code only works for disk added with:
> -drive file=/root/disk_file,if=ide,index=0,media=disk,format=raw
>
> Since the code already have the IDE controller as `dev`, we don't need
> to use the legacy DriveInfo to find all the drive we want to unplug.
> We can simply use `blk` from the controller, as it kind of was already
> assume to be the same, by setting it to NULL.
>
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
Acked-by: John Snow <jsnow@redhat.com>
Do you need me to send a PR for this?
--js
>
> ---
> v2: coding style
>
> CC: Paul Durrant <paul@xen.org>
> CC: Stefano Stabellini <sstabellini@kernel.org>
> ---
> hw/ide/piix.c | 27 +++++++++++++--------------
> 1 file changed, 13 insertions(+), 14 deletions(-)
>
> diff --git a/hw/ide/piix.c b/hw/ide/piix.c
> index b402a936362b..b9860e35a5c4 100644
> --- a/hw/ide/piix.c
> +++ b/hw/ide/piix.c
> @@ -164,30 +164,29 @@ static void pci_piix_ide_realize(PCIDevice *dev, Error **errp)
> int pci_piix3_xen_ide_unplug(DeviceState *dev, bool aux)
> {
> PCIIDEState *pci_ide;
> - DriveInfo *di;
> int i;
> IDEDevice *idedev;
> + IDEBus *idebus;
> + BlockBackend *blk;
>
> pci_ide = PCI_IDE(dev);
>
> for (i = aux ? 1 : 0; i < 4; i++) {
> - di = drive_get_by_index(IF_IDE, i);
> - if (di != NULL && !di->media_cd) {
> - BlockBackend *blk = blk_by_legacy_dinfo(di);
> - DeviceState *ds = blk_get_attached_dev(blk);
> + idebus = &pci_ide->bus[i / 2];
> + blk = idebus->ifs[i % 2].blk;
>
> - blk_drain(blk);
> - blk_flush(blk);
> -
> - if (ds) {
> - blk_detach_dev(blk, ds);
> - }
> - pci_ide->bus[di->bus].ifs[di->unit].blk = NULL;
> + if (blk && idebus->ifs[i % 2].drive_kind != IDE_CD) {
> if (!(i % 2)) {
> - idedev = pci_ide->bus[di->bus].master;
> + idedev = idebus->master;
> } else {
> - idedev = pci_ide->bus[di->bus].slave;
> + idedev = idebus->slave;
> }
> +
> + blk_drain(blk);
> + blk_flush(blk);
> +
> + blk_detach_dev(blk, DEVICE(idedev));
> + idebus->ifs[i % 2].blk = NULL;
> idedev->conf.blk = NULL;
> monitor_remove_blk(blk);
> blk_unref(blk);
>
next prev parent reply other threads:[~2020-10-27 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 15:40 [PATCH v2] xen: rework pci_piix3_xen_ide_unplug Anthony PERARD via
2020-10-27 16:03 ` Paul Durrant
2020-10-27 17:33 ` John Snow [this message]
2020-10-28 17:19 ` Anthony PERARD via
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=e7d2fef8-a697-398e-4b3b-bf247aac01a5@redhat.com \
--to=jsnow@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=paul@xen.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.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).