[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC v3 1/1] memory: Skip bad range assertion if notifier supports a
Re: [RFC v3 1/1] memory: Skip bad range assertion if notifier supports arbitrary masks
Wed, 2 Sep 2020 13:13:32 +0800
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
On 2020/9/2 上午3:35, Peter Xu wrote:
On Tue, Sep 01, 2020 at 11:05:18AM +0800, Jason Wang wrote:
On 2020/8/21 下午10:12, Peter Xu wrote:
On Thu, Aug 20, 2020 at 10:28:00AM +0800, Jason Wang wrote:
On 2020/8/19 下午11:50, Peter Xu wrote:
On Wed, Aug 19, 2020 at 03:15:26PM +0800, Jason Wang wrote:
Yes, actually, I feel confused after reading the codes. Is notifier->start
IOVA or GPA?
In vfio.c, we did:
So it looks to me the start and end are GPA, but the assertion above check
it against IOVA which seems to be wrong ....
It should be iova; both section->offset_within_region and llend are for the
device's iova address space. Thanks,
Interesting, how can memory region know which IOVA is used by guest?
Does it need to know? :)
AFAICT what we do here is only register with the whole possible IOVA address
space (e.g., across the whole 64bit address space). Then vfio will get
notifications when there're new iova ranges mapped into it.
Right, but the whole IOVA address space should be something vIOMMU specific,
e.g for Intel it should be calculated by GAW, but I found:
which assumes UINT64_MAX.
Right. AFAICT it can be reduced to gaw width, but I don't see a problem either
even with UINT64_MAX (as long as it covers the range specified by gaw). Or did
I miss something?
Just notice this difference, for safety, maybe its better to cap it with
Btw, the naming of "vtd-ir" is kind of confusing, it should work without ir.