From: Auger Eric <eric.auger@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, eric.auger.pro@gmail.com
Subject: Re: [Qemu-devel] [PATCH v2] exec: Fix MAP_RAM for cached access
Date: Thu, 14 Jun 2018 09:24:40 +0200 [thread overview]
Message-ID: <999a4ce5-a4d9-e15c-724d-2af615c44fa3@redhat.com> (raw)
In-Reply-To: <20180614015257.GO15344@xz-mi>
Hi Peter,
On 06/14/2018 03:52 AM, Peter Xu wrote:
> On Wed, Jun 13, 2018 at 04:20:34PM +0200, Auger Eric wrote:
>> Hi Paolo,
>>
>> On 06/13/2018 03:53 PM, Paolo Bonzini wrote:
>>> On 13/06/2018 15:44, Auger Eric wrote:
>>>>> Queuing this patch. I'm not sure how I missed this, I have actually
>>>>> tested it with SMMU.
>>>> no problem. Strange also I was the only one facing the issue.
>>>
>>> No, I must have blundered it between testing and posting the patches.
>>>
>>>>> Do you also need the MemTxAttrs so that the right PCI requestor id is
>>>>> used, or do you get it from somewhere else?
>>>> which call site do you have in mind, sorry?
>>>
>>> I'm wondering if the MemoryRegionCache needs to store the MemTxAttrs.
>>> They would be passed to address_space_init_cache.
>>
>> I acknowledge I don't master this code enough but I would say MSI
>> wouldn't work already (vITS wouldn't translate them properly) if the
>> proper requester_id wasn't conveyed properly. MSI writes to the doorbell
>> are not cached I guess?
>
> I might be wrong, but I guess Paolo means the DMA part. In
> address_space_cache_init() now we are with MEMTXATTRS_UNSPECIFIED when
> translate the first time (to be cached).
Ah OK, I was focused on the requester_id mention.
>
> But I'd also guess we're fine with that now since after all we're not
> even passing the attrs into IOMMUMemoryRegionClass.translate() yet.
OK fine. This can be added later on then.
Thanks
Eric
>
> Regards,
>
next prev parent reply other threads:[~2018-06-14 7:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 13:19 [Qemu-devel] [PATCH v2] exec: Fix MAP_RAM for cached access Eric Auger
2018-06-13 13:36 ` Paolo Bonzini
2018-06-13 13:44 ` Auger Eric
2018-06-13 13:53 ` Paolo Bonzini
2018-06-13 14:20 ` Auger Eric
2018-06-14 1:52 ` Peter Xu
2018-06-14 7:24 ` Auger Eric [this message]
2018-06-26 20:29 ` Auger Eric
2018-06-27 8:26 ` Paolo Bonzini
2018-06-27 8:26 ` Auger Eric
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=999a4ce5-a4d9-e15c-724d-2af615c44fa3@redhat.com \
--to=eric.auger@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peterx@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 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).