From: John Snow <jsnow@redhat.com>
To: Jordan Hargrave <jharg93@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] ahci: map memory via device's address space instead of address_space_memory
Date: Mon, 02 Mar 2015 11:37:29 -0500 [thread overview]
Message-ID: <54F491C9.4040705@redhat.com> (raw)
In-Reply-To: <CAC1AzdcoEUtiGyCSXSf0bniUvQZ9tTeX2Vc9KQUyBfQxFV+JFg@mail.gmail.com>
On 03/02/2015 11:03 AM, Jordan Hargrave wrote:
>
>
> On Thu, Feb 26, 2015 at 4:31 PM, John Snow <jsnow@redhat.com
> <mailto:jsnow@redhat.com>> wrote:
>
> (Please don't top-post on qemu-devel: gmail is kind of awful about
> this, but if you expand the conversation while in-reply, you can
> edit beneath the quote instead of above.)
>
> On 02/26/2015 04:31 PM, Jordan Hargrave wrote:
>
> The problem is the FIS registers have stale data.
>
> SeaBIOS initialization leaves the registers:
> PORT_FIS_ADDR = 0x7fae0000
> PORT_FIS_ADDR_HI = 0x0
>
> My OS initializes DMAR page tables and then enables the IOMMU
> translation.
> Then OS initializes AHCI driver. Writes VIRTUAL DMA to FIS
> registers.
> eg. FIS DMA address is 0x10000 (maps to some hardware physical
> address
> via iommu)
>
> The OS writes 0x00 PORT_FIS_ADDR_HI -> qemu calls map_page (0x00
> << 32)
> | 0x7fae0000... 0x7fae0000 is stale, and is not in the IOMMU
> page map.
> Causes a non-recoverable IOMMU fault.
>
>
>
> OK, I see.
>
> We can probably fix this by delaying the map and having it map
> on-demand before first access, setting a dirty flag if the registers
> have changed since last use.
>
> It might be an AHCI spec violation to change this register once the
> FIS Receive Engine is active, too, so it might not be too hard of a
> change; perhaps we can just map the FIS Receive Buffer once the FRE
> is started.
>
> Did you want to send a patch, or should I?
>
> --js
>
>
> I'm not as familiar with qemu internals yet to figure out how to map the
> memory on demand. I switched order of FIS initialization in my OS
> driver for the time being. The same problem was happening with the
> PORT_ADDR_LST/PORT_ADDR_LST_HI register initialization pwas well.
Okay, I'll pick this up, then. Thanks!
next prev parent reply other threads:[~2015-03-02 16:37 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 [this message]
2015-03-12 17:41 ` John Snow
-- 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=54F491C9.4040705@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 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.