From: Anthony Liguori <aliguori@us.ibm.com>
To: "Hervé Poussineau" <hpoussin@reactos.org>
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 10:37:11 -0500 [thread overview]
Message-ID: <87r4rq39p4.fsf@codemonkey.ws> (raw)
In-Reply-To: <50194975.1060306@reactos.org>
Hervé Poussineau <hpoussin@reactos.org> writes:
> Anthony Liguori a écrit :
>> On 07/06/2012 04:53 PM, Hervé Poussineau wrote:
>>> Debug output ports (enabled by DEBUG_BIOS define) can be replaced by:
>>> -chardev stdio,id=debugcon,mux=on
>>> -device isa-debugcon,iobase=0x402,chardev=debugcon
>>> -device isa-debugcon,iobase=0x403,chardev=debugcon
>>> -device isa-debugcon,iobase=0x500,chardev=debugcon
>>> -device isa-debugcon,iobase=0x503,chardev=debugcon
>>>
>>> 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
>>>
>>> Signed-off-by: Hervé Poussineau<hpoussin@reactos.org>
>>> ---
>>>
>>> Anthony, this patch is a follow-up of a patch I sent in March 2012:
>>> http://lists.gnu.org/archive/html/qemu-devel/2012-03/msg00031.html
>>>
>>> Will you accept this approach, where your regression suite will require
>>> a new parameter "-device isa-debugexit,iobase=0x501" ?
>>>
>
> [...]
>
>>>
>>> @@ -602,18 +577,8 @@ static void *bochs_bios_init(void)
>>> uint64_t *numa_fw_cfg;
>>> int i, j;
>>>
>>> - register_ioport_write(0x400, 1, 2, bochs_bios_write, NULL);
>>> - register_ioport_write(0x401, 1, 2, bochs_bios_write, NULL);
>>> - register_ioport_write(0x402, 1, 1, bochs_bios_write, NULL);
>>> - register_ioport_write(0x403, 1, 1, bochs_bios_write, NULL);
>>> register_ioport_write(0x8900, 1, 1, bochs_bios_write, NULL);
>>>
>>> - register_ioport_write(0x501, 1, 1, bochs_bios_write, NULL);
>>> - register_ioport_write(0x501, 1, 2, bochs_bios_write, NULL);
>>> - register_ioport_write(0x502, 1, 2, bochs_bios_write, NULL);
>>> - register_ioport_write(0x500, 1, 1, bochs_bios_write, NULL);
>>> - register_ioport_write(0x503, 1, 1, bochs_bios_write, NULL);
>>> -
>>> fw_cfg = fw_cfg_init(BIOS_CFG_IOPORT, BIOS_CFG_IOPORT + 1, 0, 0);
>>>
>>> fw_cfg_add_i32(fw_cfg, FW_CFG_ID, 1);
>>
>> Removing this from the default PC breaks compatibility. I don't mind
>> having a way to disable it but it needs to be there by default.
>>
>> Among other things, my test suite depends on these ports.
>>
>
> OK for keeping them on compat PC machines.
> 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.
Regards,
Anthony Liguori
>
> Regards,
>
> Hervé
next prev parent reply other threads:[~2012-08-01 15:45 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 [this message]
2012-08-01 15:48 ` Hervé Poussineau
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=87r4rq39p4.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=hpoussin@reactos.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).