From: John Snow <jsnow@redhat.com>
To: Jordan Hargrave <jharg93@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ahci: map memory via device's address space instead of address_space_memory
Date: Thu, 12 Mar 2015 13:41:12 -0400 [thread overview]
Message-ID: <5501CFB8.6090801@redhat.com> (raw)
In-Reply-To: <CAC1AzdfOy+3poMaH_4at-tfVy+fg4rpNN10zbQD4Oj28sZCuPg@mail.gmail.com>
On 02/26/2015 12:13 AM, Jordan Hargrave wrote:
> Referencing this old thread:
> https://lists.nongnu.org/archive/html/qemu-devel/2014-07/msg00606.html
>
> I've run into an issue recently with testing q35 DMAR/intel iommu with
> ahci driver. My ahci driver writes the upper-32 bits (PORT_FIS_ADDR_HI)
> first then the lower 32-bits (PORT_FIS_ADDR).
>
> The contents of PORT_FIS_ADDR therefore are stale when the
> PORT_FIS_ADDR_HI write calls map_page(). DMAR translation fails at this
> point as the old stale address (from SEABIOS initialization) is not in
> the DMAR page table.
>
Hi: I posted a fix, but do you mind elaborating on what the failure
actually looked like?
Did QEMU abort, did the guest crash, etc? What exact behavior did you
observe?
Do you have a command line to share with us?
--js
next prev parent reply other threads:[~2015-03-12 17:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 5:13 [Qemu-devel] [PATCH] ahci: map memory via device's address space instead of address_space_memory Jordan Hargrave
2015-02-26 14:45 ` Stefan Hajnoczi
2015-02-26 21:31 ` Jordan Hargrave
2015-02-26 22:02 ` Paolo Bonzini
2015-03-09 22:42 ` John Snow
2015-02-26 22:31 ` John Snow
[not found] ` <CAC1AzdcoEUtiGyCSXSf0bniUvQZ9tTeX2Vc9KQUyBfQxFV+JFg@mail.gmail.com>
2015-03-02 16:37 ` John Snow
2015-03-12 17:41 ` John Snow [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-03 8:26 Le Tan
2014-07-03 8:28 ` Michael S. Tsirkin
2014-07-03 8:47 ` Paolo Bonzini
2014-07-03 8:43 ` Jan Kiszka
2014-07-03 9:41 ` Paolo Bonzini
2014-07-03 10:11 ` Michael S. Tsirkin
2014-07-03 10:02 ` Michael S. Tsirkin
2014-07-03 16:45 ` Jan Kiszka
2014-07-03 20:30 ` Michael S. Tsirkin
2014-07-04 5:26 ` Jan Kiszka
2014-07-06 5:58 ` Michael S. Tsirkin
2014-07-07 8:23 ` Stefan Hajnoczi
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=5501CFB8.6090801@redhat.com \
--to=jsnow@redhat.com \
--cc=jharg93@gmail.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).