From: Vasilis Liaskovitis <vliaskov@gmail.com>
To: Marcel Apfelbaum <marcel.a@redhat.com>
Cc: jan.kiszka@web.de, knut.omang@oracle.com, qemu-devel@nongnu.org,
mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] qtest/bios-tables: Add DMAR unit test on intel_iommu for q35
Date: Tue, 2 Dec 2014 13:26:24 +0100 [thread overview]
Message-ID: <20141202122624.GA2828@clowntown> (raw)
In-Reply-To: <1416839105.20462.33.camel@localhost.localdomain>
On Mon, Nov 23, 2014 at 04:25:05PM +0200, Marcel Apfelbaum wrote:
> On Mon, 2014-11-24 at 14:37 +0100, Vasilis Liaskovitis wrote:
> > The test enables intel_iommu on q35, looks for and reads the DMAR table as well
> > as its only DRHC structure (for now), checking the header and checksums.
>
> Hi Vaisilis,
> I had a deeper look to your patch and the code already checks
> header and checksum for DMAR, all you had to do is to add your latest chunk:
>
> @@ -779,7 +823,7 @@ static void test_acpi_tcg(void)
> >
> > memset(&data, 0, sizeof(data));
> > data.machine = MACHINE_Q35;
> > - test_acpi_one("-machine q35,accel=tcg", &data);
> > + test_acpi_one("-machine q35,accel=tcg,iommu=on", &data);
> > free_test_data(&data);
>
> You can check that it is automatically done by test_dst_table function.
> You can add there a print to convince yourself.
>
> However what is missing is a DMAR binary table to compare the content with an expected one.
> You can create it by running:
> tests/acpi-test-data/rebuild-expected-aml.sh
>
> Then add the newly created file to tests/acpi-test-data/q35/DMAR
sorry for the delay. thanks, I missed this. I sent v3 simply with the addition
of the DMAR aml file and just the "iommu=on" chunk, as you suggested.
- Vasilis
prev parent reply other threads:[~2014-12-02 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 13:37 [Qemu-devel] [PATCH v2] qtest/bios-tables: Add DMAR unit test on intel_iommu for q35 Vasilis Liaskovitis
2014-11-24 14:25 ` Marcel Apfelbaum
2014-12-02 12:26 ` Vasilis Liaskovitis [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=20141202122624.GA2828@clowntown \
--to=vliaskov@gmail.com \
--cc=jan.kiszka@web.de \
--cc=knut.omang@oracle.com \
--cc=marcel.a@redhat.com \
--cc=mst@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 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.