qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "lmr@redhat.com" <lmr@redhat.com>,
	"Hervé Poussineau" <hpoussin@reactos.org>,
	qemu-devel@nongnu.org, "Anthony Liguori" <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PULL 0/4] test and debug devices
Date: Fri, 04 Jan 2013 14:07:15 +0100	[thread overview]
Message-ID: <50E6D403.4070900@suse.de> (raw)
In-Reply-To: <50E6D1B1.7010608@redhat.com>

Hi Gerd,

Am 04.01.2013 13:57, schrieb Gerd Hoffmann:
>>> This patch series improves the debug devices we have.  isa-debugcon is
>>> switched over to the memory api.  isa-debug-exit is added and replaces
>>> the hard-coded bochs debug port.  pc-testdev (used by kvm-unit-tests) is
>>> added.
>>
>> Missing some CCs, and I was actually expecting another PATCH series
>> first... as brought up before it is refreshing an uncommitted series by
>> Hervé without any mention thereof in the commit message
> 
> Hmm?  The isa-debug-exit patch is written by myself.  After hacking it
> up I've noticed Herve wrote a simliar one.  But I didn't grab Herve's
> patch.  I've picked up + updated Lucas' testdev patch, and that is
> clearly visible in the commit message.
> 
>> and I thought
>> there was an unanswered question to Anthony on both Lucas' and Hervé's
>> series?
> 
> The only outstanding question I'm aware of is whenever anthony does a
> outb or outw on the bochs debug port in his test suite.  My
> isa-debug-exit device handles both cases, so we should be fine here, and
> I'm sure Anthony will actually try before committing the series ;)
> 
> What else is unanswered?

I believe the original unanswered question was whether it is okay for
Anthony to add -device foo for his testing now that the default port was
changed to what he was relying on or whether he wants it to
automatically get instantiated for machine backwards compatibility
unless --no-defaults (or whatever it's called) is used. Your series,
just like Hervé's that got stopped by Anthony, simple moves things into
a standalone device in 2/4 and I don't see any pc-1.3 handling in 4/4.

Cheers,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-01-04 13:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04  8:16 [Qemu-devel] [PULL 0/4] test and debug devices Gerd Hoffmann
2013-01-04  8:16 ` [Qemu-devel] [PATCH 1/4] switch debugcon to memory api Gerd Hoffmann
2013-01-06 18:03   ` Andreas Färber
2013-01-04  8:16 ` [Qemu-devel] [PATCH 2/4] add isa-debug-exit device Gerd Hoffmann
2013-01-04  8:16 ` [Qemu-devel] [PATCH 3/4] hw: Add test device for unittests execution Gerd Hoffmann
2013-01-04 21:44   ` Stefan Weil
2013-01-04 22:38     ` Alexander Graf
2013-01-06 18:19   ` Andreas Färber
2013-01-04  8:16 ` [Qemu-devel] [PATCH 4/4] pc: remove bochs bios debug ports Gerd Hoffmann
2013-01-04 10:28 ` [Qemu-devel] [PULL 0/4] test and debug devices Andreas Färber
2013-01-04 12:57   ` Gerd Hoffmann
2013-01-04 13:07     ` Andreas Färber [this message]
2013-01-04 13:45     ` Anthony Liguori
2013-01-04 20:21 ` 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=50E6D403.4070900@suse.de \
    --to=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=hpoussin@reactos.org \
    --cc=kraxel@redhat.com \
    --cc=lmr@redhat.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).