All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Mike Belopuhov <mike.belopuhov@esdenera.com>, xen-devel@lists.xen.org
Subject: Re: Sub page Grant Table mappings
Date: Tue, 22 Dec 2015 21:08:01 +0000	[thread overview]
Message-ID: <5679BBB1.3020100@citrix.com> (raw)
In-Reply-To: <20151222205910.GA24365@kemushi.esdenera.com>

On 22/12/15 20:59, Mike Belopuhov wrote:
> Hi,
>
> I'm trying to get grant table sub page mappings working on Xen 4.5.
> I know there have been some changes in the trunk regarding moving src/
> dst checks closer together, but I can't test this easily atm.  Please
> bear with me for a moment.  Or tell me that it might have been broken
> previously.
>
> What I'm trying to do is to map in a 2k cluster from the networking
> stack (we call it an mbuf cluster, you might call it skb something)
> onto the Netfront Rx ring.  2 clusters fit one page.  Therefore for
> one frame address which is a (PA >> 12) I might have 2 entries one
> after the other, both with sub_page.length = 2048 but one with a
> sub_page.page_off = 2048 and the other with a 0 offset.  Both come
> with (GTF_permit_access | GTF_sub_page) flags.
>
> When I do that, Xen stops liking me and says:
>
> (XEN) grant_table.c:2162:d0v1 copy dest out of bounds: 0 < 2048 || 90 > 2048
> (XEN) grant_table.c:2162:d0v1 copy dest out of bounds: 0 < 2048 || 119 > 2048
> (XEN) grant_table.c:2162:d0v2 copy dest out of bounds: 0 < 2048 || 70 > 2048
> (XEN) grant_table.c:2162:d0v2 copy dest out of bounds: 0 < 2048 || 119 > 2048
> (XEN) grant_table.c:2162:d0v2 copy dest out of bounds: 0 < 2048 || 119 > 2048
> ...
>
> The relevant code does this:
>
>     if ( dest_is_gref )
>     {
>         unsigned dest_off, dest_len;
>         rc = __acquire_grant_for_copy(dd, op->dest.u.ref,
>                                       current->domain->domain_id, 0,
>                                       &d_frame, &d_pg, &dest_off, &dest_len, 1);
>         if ( rc != GNTST_okay )
>             goto error_out;
>         have_d_grant = 1;
>         if ( op->dest.offset < dest_off ||
>              op->len > dest_len )
>             PIN_FAIL(error_out, GNTST_general_error,
>                      "copy dest out of bounds: %d < %d || %d > %d\n",
>                      op->dest.offset, dest_off,
>                      op->len, dest_len);
>     }
>
> I fail to understand what am I doing wrong in this case.  Any clues
> will be greatly appreciated.
>
> 4k clusters mapped in as full_page mappings work as expected.
>
> Cheers,
> Mike

I presume you are on x86 here.

Architecturally, a 4k page is the minimum granularity which permissions
can be applied to.  It is not possible to make a 2k block accessible,
but an adjacent 2k block inaccessible.

As a result, grant mapping of a subpage grant is prohibited, but you are
(or at least should be) able to grant copy it.

Can you describe precisely which domains are doing what in your example?

~Andrew

  reply	other threads:[~2015-12-22 21:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 20:59 Sub page Grant Table mappings Mike Belopuhov
2015-12-22 21:08 ` Andrew Cooper [this message]
2015-12-22 22:55 ` Mike Belopuhov
2015-12-23 10:06 ` David Vrabel

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=5679BBB1.3020100@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=mike.belopuhov@esdenera.com \
    --cc=xen-devel@lists.xen.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.