qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Pavel Butsykin <pbutsykin@odin.com>, "Denis V. Lunev" <den@openvz.org>
Cc: "Markus Armbruster" <armbru@redhat.com>,
	"Luiz Capitulino" <lcapitulino@redhat.com>,
	qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>,
	"Pavel Butsykin" <pbutsykin@virtuozzo.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/9] hmp command IO- and Local APIC dump state
Date: Tue, 22 Sep 2015 13:09:59 +0200	[thread overview]
Message-ID: <56013707.7000704@redhat.com> (raw)
In-Reply-To: <5601319F.30400@odin.com>



On 22/09/2015 12:46, Pavel Butsykin wrote:
>>>
>> I would print IRR as a bitmap here, like ISR/IRR in the local APIC dump.
>>   Similarly, it would be nice to print the "Remote IRR" bits of the
>> redirection table (printing them as a bitmap with the same format).
> ...
> 
> pin 9  0x0000000000018041 dest=0 vec=65  active-hi level IRR(0) masked
> fixed  physical
> pin 10 0x0000000000010000 dest=0 vec=0   active-hi edge         masked
> fixed  physical
> pin 11 0x0300000000008081 dest=3 vec=129 active-hi level IRR(0)       
> fixed  physical
> pin 12 0x000000000000003c dest=0 vec=60  active-hi edge               
> fixed  physical
> ...
> IRR 2 17

I was thinking more like:

pin 9  0x0000000000018041 dest=0 vec=65  active-hi level masked fixed
physical
pin 10 0x0000000000010000 dest=0 vec=0   active-hi edge  masked fixed
physical
pin 11 0x030000000000c081 dest=3 vec=129 active-hi level        fixed
physical
pin 12 0x000000000000003c dest=0 vec=60  active-hi edge         fixed
physical
...
IRR         2 17
Remote IRR  11

Paolo

      reply	other threads:[~2015-09-22 11:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 10:57 [Qemu-devel] [PATCH v3 0/9] hmp command IO- and Local APIC dump state Denis V. Lunev
2015-09-21 10:57 ` [Qemu-devel] [PATCH 1/9] apic_internal.h: make some apic_get_* functions externally visible Denis V. Lunev
2015-09-21 10:57 ` [Qemu-devel] [PATCH 2/9] apic_internal.h: rename ESR_ILLEGAL_ADDRESS to APIC_ESR_ILLEGAL_ADDRESS Denis V. Lunev
2015-09-21 10:57 ` [Qemu-devel] [PATCH 3/9] apic_internal.h: added more constants Denis V. Lunev
2015-09-21 10:57 ` [Qemu-devel] [PATCH 4/9] apic_internal.h: fix formatting and drop unused consts Denis V. Lunev
2015-09-21 10:57 ` [Qemu-devel] [PATCH 5/9] monitor: make monitor_fprintf and mon_get_cpu externally visible Denis V. Lunev
2015-09-21 10:57 ` [Qemu-devel] [PATCH 6/9] hmp: added local apic dump state Denis V. Lunev
2015-09-21 10:57 ` [Qemu-devel] [PATCH 7/9] ioapic_internal.h: added more constants Denis V. Lunev
2015-09-21 10:57 ` [Qemu-devel] [PATCH 8/9] hmp: added io apic dump state Denis V. Lunev
2015-09-21 10:57 ` [Qemu-devel] [PATCH 9/9] hmp: implemented io apic dump state for TCG Denis V. Lunev
2015-09-21 13:59 ` [Qemu-devel] [PATCH v3 0/9] hmp command IO- and Local APIC dump state Paolo Bonzini
2015-09-22 10:46   ` Pavel Butsykin
2015-09-22 11:09     ` Paolo Bonzini [this message]

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=56013707.7000704@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=armbru@redhat.com \
    --cc=den@openvz.org \
    --cc=lcapitulino@redhat.com \
    --cc=pbutsykin@odin.com \
    --cc=pbutsykin@virtuozzo.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).