From: John Snow <jsnow@redhat.com>
To: zhaoxinRockCuioc <RockCui-oc@zhaoxin.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
CobeChen@zhaoxin.com, Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH] ide:do nothing for identify cmd if no any device attached
Date: Wed, 2 Sep 2020 14:02:22 -0400 [thread overview]
Message-ID: <8dbcc856-879a-af83-1a76-a2a875da3699@redhat.com> (raw)
In-Reply-To: <20200817033803.14014-1-RockCui-oc@zhaoxin.com>
(CC Max for block backend model confusion, see below)
On 8/16/20 11:38 PM, zhaoxin\RockCuioc wrote:
> This patch is for avoiding win7 IDE driver polling 0x1f7 when
> no any device attached. During Win7 VM boot procedure, if use virtio for
> disk and there is no any device be attached on hda & hdb, the win7 IDE driver
> would poll 0x1f7 for a while. This action may be stop windows LOGO atomic for
> a while too on a poor performance CPU.
>
A few questions:
(1) How slow is the probing?
(2) If there are no devices attached, why don't you remove the IDE
controller so that Windows doesn't have to probe it?
> Signed-off-by: zhaoxin\RockCuioc <RockCui-oc@zhaoxin.com>
> ---
> hw/ide/core.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/hw/ide/core.c b/hw/ide/core.c
> index d997a78e47..26d86f4b40 100644
> --- a/hw/ide/core.c
> +++ b/hw/ide/core.c
> @@ -2073,8 +2073,9 @@ void ide_exec_cmd(IDEBus *bus, uint32_t val)
> s = idebus_active_if(bus);
> trace_ide_exec_cmd(bus, s, val);
>
> - /* ignore commands to non existent slave */
> - if (s != bus->ifs && !s->blk) {
> + /* ignore commands if no any device exist or non existent slave */
> + if ((!bus->ifs[0].blk && !bus->ifs[1].blk) ||
> + (s != bus->ifs && !s->blk)) {
> return;
> }
>
I think it's the case that Empty CD-ROM drives will have an anonymous
block backend representing the empty drive, so I suppose this is maybe fine?
I suppose the idea is that with no drives on the bus that it's fine to
ignore the register writes, as there are no devices to record those writes.
(But then, why did we ever only check device1? ...)
Maybe before the block-backend split we used to have to check to see if
we had attached media or not, but I think nowadays we should always have
a blk pointer if we have a device model intended to be operating at this
address.
So I guess it can be simplified ...?
if (!s->blk) {
return;
}
--js
next prev parent reply other threads:[~2020-09-02 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 3:38 [PATCH] ide:do nothing for identify cmd if no any device attached zhaoxin\RockCuioc
2020-08-17 4:15 ` no-reply
2020-09-02 18:02 ` John Snow [this message]
2020-09-03 10:40 ` Max Reitz
2020-09-09 3:13 ` 答复: " RockCui-oc
2020-10-02 19:37 ` John Snow
2020-11-12 7:29 ` 答复: " RockCui-oc
-- strict thread matches above, loose matches on Subject: below --
2020-08-14 4:36 zhaoxin\RockCuioc
2020-08-14 15:25 ` no-reply
2020-08-14 15:43 ` no-reply
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=8dbcc856-879a-af83-1a76-a2a875da3699@redhat.com \
--to=jsnow@redhat.com \
--cc=CobeChen@zhaoxin.com \
--cc=RockCui-oc@zhaoxin.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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 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).