qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: lcapitulino@redhat.com, Avi Kivity <avi@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv2] add "info ioapic" monitor command
Date: Fri, 1 Jan 2010 12:27:52 +0200	[thread overview]
Message-ID: <20100101102752.GF9233@redhat.com> (raw)
In-Reply-To: <4B3CF5EE.8090602@codemonkey.ws>

On Thu, Dec 31, 2009 at 01:05:18PM -0600, Anthony Liguori wrote:
> On 12/31/2009 09:42 AM, Gleb Natapov wrote:
> >On Thu, Dec 31, 2009 at 08:20:06AM -0600, Anthony Liguori wrote:
> >>On 12/30/2009 06:20 PM, Gleb Natapov wrote:
> >>>I included only the state I need for debugging. I don't what to see
> >>>complete state. It will just clatter important info.
> >>
> >>Someone may find that full state useful though.  There's no good
> >>reason to not show the entire device's state.
> >>
> >There is no good reason to not show the entire device's state in
> >addition to nicely formated most useful part of it. Here I fixed it for
> >you.
> 
> 
> Have you even attempted to look at what the generic implementation
> would be? ioapic has three vmstate fields.  If you decode ioredtbl
> into six subfields, then you're only adding two addition fields to
> be printed.
> 
I you seriously suggesting that we should tie the way device state is
migrated to the way device information is printed? 

> I can't believe that having those two extra fields is really going
> to make it any more difficult to debug.
> 
Can't parse that.

> And being able to dump any device state is certainly going to be
> useful in the future.
> 
No arguing with that.

--
			Gleb.

           reply	other threads:[~2010-01-01 10:28 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <4B3CF5EE.8090602@codemonkey.ws>]

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=20100101102752.GF9233@redhat.com \
    --to=gleb@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=lcapitulino@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).