qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: 'Peter Maydell' <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org, 'Paolo Bonzini' <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/3] Make KVM/MSI code device-ID-aware
Date: Wed, 14 Oct 2015 14:59:11 +0300	[thread overview]
Message-ID: <20151014145852-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <013d01d10676$59b7cb60$0d276220$@samsung.com>

On Wed, Oct 14, 2015 at 02:49:14PM +0300, Pavel Fedin wrote:
>  Hello!
> 
> > OK, so we could rename stream id to requester id. That at least would
> > make sense at the pci level, and would make it unique per hierarchy.
> 
>  Yes, we can, i'm fine with the rename. Additionally, "requester ID" is the official term used in GICv3 architecture manual. When i
> implemented it i didn't have arch manual, therefore had to invent the name.
> 
> > But I suspect all these optimizations break later when we need to support
> > multiple root complex devices.
> 
>  Not necessarily. IIRC we have three bits used for other purposes in MemTxAttrs. So, we could extend our RID up to 24 bits and still
> be fine. Even if we use 32 bits, our MemTxAttrs would still fit into register on 64-bit platforms, and into two registers on 32-bit
> platforms. The same as MSIMessage (don't remember exact name).
> 
>  Should i post v3, including the rename, or will you just rename stream_id to requester_id yourself?
> 
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia


Pls do it.

-- 
MST

      reply	other threads:[~2015-10-14 11:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14  7:53 [Qemu-devel] [PATCH v2 0/3] Make KVM/MSI code device-ID-aware Pavel Fedin
2015-10-14  7:53 ` [Qemu-devel] [PATCH v2 1/3] kvm: Make KVM_CAP_SIGNAL_MSI globally available Pavel Fedin
2015-10-14  7:53 ` [Qemu-devel] [PATCH v2 2/3] hw/pci: Introduce msi_device_id() Pavel Fedin
2015-10-14  7:53 ` [Qemu-devel] [PATCH v2 3/3] kvm: Pass PCI device pointer to MSI routing functions Pavel Fedin
2015-10-14  8:32 ` [Qemu-devel] [PATCH v2 0/3] Make KVM/MSI code device-ID-aware Michael S. Tsirkin
2015-10-14  8:46   ` Pavel Fedin
2015-10-14 10:44     ` Michael S. Tsirkin
2015-10-14 11:49       ` Pavel Fedin
2015-10-14 11:59         ` Michael S. Tsirkin [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=20151014145852-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=p.fedin@samsung.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.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).