All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: "David Kiarie" <davidkiarie4@gmail.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Marcel Apfelbaum" <marcel@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Eduardo Habkost" <ehabkost@redhat.com>
Cc: Valentine Sinitsyn <valentine.sinitsyn@gmail.com>
Subject: Re: [Qemu-devel] Question on Qemu IOAPIC ID
Date: Sat, 30 Jul 2016 09:41:31 +0200	[thread overview]
Message-ID: <0b6b2cc4-8eb7-28ec-30e9-2832e96587a2@web.de> (raw)
In-Reply-To: <CABdVeAARtuphr3X6CXrM8NVLS9J4p_SqWzQHXg2Uzv9MvXuxkw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

On 2016-07-23 10:12, David Kiarie wrote:
> Hello all,
> 
> I, working on AMD IOMMU interrupt remapping would like to ask some
> questions on Qemu IOAPIC id.
> 
> I currently have a problem in that Linux AMD IOMMU driver expects at least
> one IOAPIC on the chipset to have ID 0xa0 while Qemu IOAPIC id is always 0.
> I am faced with two options
>    -Change IOAPIC id so that it always matches what Linux AMD IOMMU driver
> expects. In this case I am not sure which problems I could encounter with
> this approach.
>    -Have a way to configure IOAPIC ID based on emulated IOMMU.
> 
> I prefer the first approach since it's quite simple but would like to hear
> other opinions regarding this issue.
> 
> David.
> 

Ping on this question by David:

If we can consolidate over AMD's IOAPIC ID now, before releasing 4.7
(later changes would be guest visible), we won't have to add a special
case for the AMD IOMMU later.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-07-30  7:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-23  8:12 [Qemu-devel] Question on Qemu IOAPIC ID David Kiarie
2016-07-30  7:41 ` Jan Kiszka [this message]
2016-07-30  9:23   ` Jan Kiszka

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=0b6b2cc4-8eb7-28ec-30e9-2832e96587a2@web.de \
    --to=jan.kiszka@web.de \
    --cc=davidkiarie4@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rkrcmar@redhat.com \
    --cc=valentine.sinitsyn@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.