From: Julien Grall <julien.grall@arm.com>
To: Oleksandr Tyshchenko <olekstysh@gmail.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Andrushchenko <andr2000@gmail.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Andrii Anisov <andrii.anisov@gmail.com>,
Volodymyr Babchuk <vlad.babchuk@gmail.com>,
al1img <al1img@gmail.com>,
xen-devel@lists.xenproject.org,
Artem Mygaiev <joculator@gmail.com>
Subject: Re: Shattering superpages impact on IOMMU in Xen
Date: Thu, 6 Apr 2017 21:39:26 +0100 [thread overview]
Message-ID: <ad901b30-917c-5912-2662-86263e14eaec@arm.com> (raw)
In-Reply-To: <CAPD2p-nBGJM-N=eY_kYLbErhZpZTqOK++UwQCagwfySd7gWnPg@mail.gmail.com>
Hi Oleksandr,
Please try to configure the mail client to quote with '>'. Using tab for
quoting make it quite difficult to follow.
On 04/06/2017 09:36 PM, Oleksandr Tyshchenko wrote:
> 6 апр. 2017 г. 22:22 пользователь "Julien Grall" <julien.grall@arm.com
> <mailto:julien.grall@arm.com>> написал:
> If the IOMMU is not able to snoop the cache, then the way forward is
> to use a clean_dcache operation after writing a page table entry.
> This is how we deal in the p2m code.
>
> Agree.
>
> As we update page table in an atomic way (no BBM sequence) and the
> reason caused page faults was found, I think that the IPMMU driver can
> declare superpage capability?
Yes for the IPMMU driver. Although we would have to do some things for
the SMMU driver.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-04-06 20:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 16:24 Shattering superpages impact on IOMMU in Xen Oleksandr Tyshchenko
2017-04-03 16:42 ` Andrew Cooper
2017-04-03 17:02 ` Julien Grall
2017-04-03 17:16 ` Andrew Cooper
2017-04-03 18:06 ` Julien Grall
2017-04-03 18:21 ` Oleksandr Tyshchenko
2017-04-03 20:33 ` Stefano Stabellini
2017-04-04 9:28 ` Oleksandr Tyshchenko
2017-04-06 18:59 ` Oleksandr Tyshchenko
2017-04-06 19:22 ` Julien Grall
2017-04-06 20:36 ` Oleksandr Tyshchenko
2017-04-06 20:39 ` Julien Grall [this message]
2017-04-03 17:39 ` Oleksandr Tyshchenko
2017-04-03 17:53 ` Oleksandr Tyshchenko
2017-04-03 18:26 ` Oleksandr Tyshchenko
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=ad901b30-917c-5912-2662-86263e14eaec@arm.com \
--to=julien.grall@arm.com \
--cc=al1img@gmail.com \
--cc=andr2000@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=andrii.anisov@gmail.com \
--cc=joculator@gmail.com \
--cc=olekstysh@gmail.com \
--cc=sstabellini@kernel.org \
--cc=vlad.babchuk@gmail.com \
--cc=xen-devel@lists.xenproject.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).