From: David Vrabel <david.vrabel@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] xen-blkback: only attach blkback if the required features are met
Date: Fri, 4 Apr 2014 16:01:58 +0100 [thread overview]
Message-ID: <533EC966.7030101@citrix.com> (raw)
In-Reply-To: <1396622471-13114-1-git-send-email-roger.pau@citrix.com>
On 04/04/14 15:41, Roger Pau Monne wrote:
> Blkback cannot work properly on auto-translated guests if Xen doesn't
> update the IOMMU when performing grant maps/unmaps, so only attach if
> the newly introduced XENFEAT_hvm_gntmap_supports_iommu is found.
Can you explain the problem in more detail and which guest
configurations are affected?
This isn't a problem that is specific to blkback, but any backend that
grant maps and passes the foreign pages to a device so there needs to be
a generic solution.
Why can't this be fixed by having the swiotlb bounce foreign pages?
> --- a/drivers/block/xen-blkback/blkback.c
> +++ b/drivers/block/xen-blkback/blkback.c
> @@ -1381,6 +1381,18 @@ static int __init xen_blkif_init(void)
> if (!xen_domain())
> return -ENODEV;
>
> +#ifdef CONFIG_X86
> + if (xen_feature(XENFEAT_auto_translated_physmap) &&
> + !xen_feature(XENFEAT_hvm_gntmap_supports_iommu)) {
> + /*
> + * blkback cannot work properly on auto-translated guests
> + * if grant table mappings don't update the IOMMU entries.
> + */
> + pr_debug(DRV_PFX "Disabling blkback because Xen is missing feature XENFEAT_hvm_gntmap_supports_iommu\n");
> + return -ENODEV;
> + }
> +#endif /* CONFIG_X86 */
Why CONFIG_X86?
David
next prev parent reply other threads:[~2014-04-04 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 14:41 [PATCH] xen-blkback: only attach blkback if the required features are met Roger Pau Monne
2014-04-04 15:01 ` David Vrabel [this message]
2014-04-04 15:13 ` Roger Pau Monné
2014-04-07 17:11 ` David Vrabel
2014-04-04 16:58 ` Konrad Rzeszutek Wilk
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=533EC966.7030101@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.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).