From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] hw/i386: Fix IVHD entry length for AMD IOMMU
Date: Wed, 13 Jun 2018 17:26:28 +0300 [thread overview]
Message-ID: <20180613172438-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <a2198ea1-e0f6-6b04-63a8-fd04b40c9ff2@web.de>
On Tue, May 22, 2018 at 09:06:56AM +0200, Jan Kiszka wrote:
> On 2018-03-29 14:51, Jan Kiszka wrote:
> > From: Jan Kiszka <jan.kiszka@siemens.com>
> >
> > Counting from the IVHD ID field to the all-devices entry, we have 28
> > bytes, not 36.
> >
> > Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> > ---
> > hw/i386/acpi-build.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
> > index deb440f286..a0cda71411 100644
> > --- a/hw/i386/acpi-build.c
> > +++ b/hw/i386/acpi-build.c
> > @@ -2561,7 +2561,7 @@ build_amd_iommu(GArray *table_data, BIOSLinker *linker)
> > (1UL << 7), /* PPRSup */
> > 1);
> > /* IVHD length */
> > - build_append_int_noprefix(table_data, 0x24, 2);
> > + build_append_int_noprefix(table_data, 28, 2);
> > /* DeviceID */
> > build_append_int_noprefix(table_data, s->devid, 2);
> > /* Capability offset */
> >
>
> Waiting to be merged.
>
> Jan
I'll queue this but you really should Cc maintainers :)
--
MST
next prev parent reply other threads:[~2018-06-13 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 12:51 [Qemu-devel] [PATCH] hw/i386: Fix IVHD entry length for AMD IOMMU Jan Kiszka
2018-03-31 7:32 ` no-reply
2018-03-31 8:59 ` Jan Kiszka
2018-05-22 7:06 ` Jan Kiszka
2018-06-13 14:26 ` Michael S. Tsirkin [this message]
2018-06-13 14:39 ` 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=20180613172438-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jan.kiszka@web.de \
--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 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.