From: "Hervé Poussineau" <hpoussin@reactos.org>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] pc: remove DEBUG_BIOS define and QEMU exit I/O ports
Date: Wed, 01 Aug 2012 17:48:46 +0200 [thread overview]
Message-ID: <50194FDE.50806@reactos.org> (raw)
In-Reply-To: <87r4rq39p4.fsf@codemonkey.ws>
Anthony Liguori a écrit :
> Hervé Poussineau <hpoussin@reactos.org> writes:
>
>> Anthony Liguori a écrit :
>>> On 07/06/2012 04:53 PM, Hervé Poussineau wrote:
>>>> QEMU exit (which can be guest triggered) can be replaced by:
>>>> -device isa-debugexit,iobase=0x501
>>>> -device isa-debugexit,iobase=0x501,access-size=2
>>>> -device isa-debugexit,iobase=0x502,access-size=2
>>>>
[...]
>> However, for current ones (1.2 or later), I don't want to have them by
>> default as it is an QEMU exit which is guest triggerable.
>> Will you accept this approach, where your regression suite will require
>> a new parameter "-device isa-debugexit,iobase=0x501" ?
>
> Yes although I'd prefer the iobase not be required to be explicitly
> specified.
Which one are you using? iobase 0x501 or 0x502? And with access size 1 or 2?
Regards,
Hervé
next prev parent reply other threads:[~2012-08-01 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 21:53 [Qemu-devel] [PATCH 1/2] debugexit: support for custom exit port (e.g LGPL'ed VGA BIOS port 0x501) Hervé Poussineau
2012-07-06 21:53 ` [Qemu-devel] [PATCH 2/2] pc: remove DEBUG_BIOS define and QEMU exit I/O ports Hervé Poussineau
2012-07-29 11:33 ` Hervé Poussineau
2012-08-01 13:59 ` Anthony Liguori
2012-08-01 15:21 ` Hervé Poussineau
2012-08-01 15:37 ` Anthony Liguori
2012-08-01 15:48 ` Hervé Poussineau [this message]
2012-09-11 14:50 ` Andreas Färber
2012-09-11 18:30 ` Hervé Poussineau
2012-08-01 14:30 ` [Qemu-devel] [PATCH 1/2] debugexit: support for custom exit port (e.g LGPL'ed VGA BIOS port 0x501) Andreas Färber
2012-08-01 14:58 ` Anthony Liguori
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=50194FDE.50806@reactos.org \
--to=hpoussin@reactos.org \
--cc=aliguori@us.ibm.com \
--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).