From: "Andreas Färber" <afaerber@suse.de>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Anthony Liguori" <aliguori@us.ibm.com>,
qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
"Blue Swirl" <blauwirbel@gmail.com>,
"Hervé Poussineau" <hpoussin@reactos.org>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] ide: log error when trying to use ATAPI overlapping features
Date: Mon, 11 Feb 2013 15:19:21 +0100 [thread overview]
Message-ID: <5118FDE9.2000101@suse.de> (raw)
In-Reply-To: <87k3qf9cg8.fsf@blackfin.pond.sub.org>
Am 11.02.2013 15:01, schrieb Markus Armbruster:
> Kevin Wolf <kwolf@redhat.com> writes:
>
>> Am 11.02.2013 14:27, schrieb Stefan Hajnoczi:
>>> On Sun, Feb 10, 2013 at 11:12:11PM +0100, Hervé Poussineau wrote:
>>>>
>>>> Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
>>>> ---
>>>> hw/ide/core.c | 4 +++-
>>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/hw/ide/core.c b/hw/ide/core.c
>>>> index 3743dc3..f0ab1a8 100644
>>>> --- a/hw/ide/core.c
>>>> +++ b/hw/ide/core.c
>>>> @@ -1394,8 +1394,10 @@ void ide_exec_cmd(IDEBus *bus, uint32_t val)
>>>> break;
>>>> case WIN_PACKETCMD:
>>>> /* overlapping commands not supported */
>>>> - if (s->feature & 0x02)
>>>> + if (s->feature & 0x02) {
>>>> + qemu_log_mask(LOG_UNIMP, "ide: overlapping command not supported");
>>>
>>> qemu_log_*() isn't used much in hw/.
>>>
>>> I think we need to side-track this patch email to figure out what to
>>> use:
>>>
>>> fprintf(stderr) - some warnings/errors use this
>>> error_report() - goes to the monitor, if possible, otherwise stderr
>>
>> These look wrong to me.
>
> "Wrong" is a bit strong, in particular since there's ample precedence
> for these uses.
>
>>> qemu_log_*() - goes to the qemu log, seems a little TCG-centric
>>
>> I would suggest either this or just trace points. (And by the way, it's
>> a pity that -d is so TCG-centric, it's been more than once the reason
>> why I disabled KVM when debugging a guest... Having at least -d int
>> would be so useful.)
>
> Tracepoints don't really fit when we want to report the guest does
> something we don't handle. Users deserve fair warning then, don't they?
>
> Could qemu_log() & friends be made fit for general use? What's missing?
Blue already did some work to make it more usable, and I believe Peter
adopted LOG_UNIMPL for ARM devices in place of hw_error(), which is
another reporting option people have chosen in the past (but which
allows a guest to exit the QEMU process).
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-02-11 14:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 22:12 [Qemu-trivial] [PATCH] ide: log error when trying to use ATAPI overlapping features Hervé Poussineau
2013-02-11 13:27 ` [Qemu-trivial] [Qemu-devel] " Stefan Hajnoczi
2013-02-11 13:33 ` Kevin Wolf
2013-02-11 14:01 ` Markus Armbruster
2013-02-11 14:19 ` Andreas Färber [this message]
2013-02-11 14:34 ` Peter Maydell
2013-02-11 14:57 ` Stefan Hajnoczi
2013-02-11 15:03 ` Peter Maydell
2013-02-11 15:10 ` Andreas Färber
2013-02-12 7:55 ` Stefan Hajnoczi
2013-02-11 15:10 ` Peter Maydell
2013-02-11 21:08 ` Hervé Poussineau
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=5118FDE9.2000101@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=hpoussin@reactos.org \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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.