xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel@lists.xen.org
Cc: sstabellini@kernel.org
Subject: Re: [PATCH for-4.10 2/2] xen/arm: p2m: Add more debug in get_page_from_gva
Date: Wed, 15 Nov 2017 21:42:44 +0000	[thread overview]
Message-ID: <d25edbc4-85a2-7219-a66a-bde3c15861ee@linaro.org> (raw)
In-Reply-To: <53a2b243-7132-2527-f72c-d046a869fae6@citrix.com>

Hi Andrew,

On 11/15/2017 07:43 PM, Andrew Cooper wrote:
> On 15/11/17 19:34, Julien Grall wrote:
>> The function get_page_from_gva is used by copy_*_guest helpers to
>> translate a guest virtual address to a machine physical address and take
>> reference on the page.
>>
>> There are a couple of errors path that will return the same value making
>> difficult to know the exact error. Add more debug in each error patch
>> only for debug-build.
>>
>> This should help narrowing down the intermittent failure with the
>> hypercall GNTTABOP_copy (see [1]).
>>
>> [1] https://lists.xen.org/archives/html/xen-devel/2017-11/msg00942.html
>>
>> Signed-off-by: Julien Grall <julien.grall@linaro.org>
>> ---
>>   xen/arch/arm/p2m.c | 13 +++++++++++++
>>   1 file changed, 13 insertions(+)
>>
>> diff --git a/xen/arch/arm/p2m.c b/xen/arch/arm/p2m.c
>> index f6b3d8e421..417609ede2 100644
>> --- a/xen/arch/arm/p2m.c
>> +++ b/xen/arch/arm/p2m.c
>> @@ -1428,16 +1428,29 @@ struct page_info *get_page_from_gva(struct vcpu *v, vaddr_t va,
>>       par = gvirt_to_maddr(va, &maddr, flags);
>>   
>>       if ( par )
>> +    {
>> +        dprintk(XENLOG_G_DEBUG,
>> +                "%pv: gvirt_to_maddr failed va=%#"PRIvaddr" flags=0x%lx par=%#"PRIx64"\n",
>> +                v, va, flags, par);
> 
> Given the long round-trip time on debugging output, how about trying to
> dump the guest and/or second stage table walk?

I thought about it, however at the moment dump_s1_guest_walk() is very 
minimal and would be add much value here. Thought, Now that we have code 
to do first-stage walk (see guest_walk_tables), we might be able to get 
a better dump here. Thought I am not sure it would be 4.10 material.

However, I think we could try to translate the guest VA to a guest PA 
using hardware instruction and then do the second-stage walk using 
dump_p2m_lookup.

Let me have a look.

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-11-15 21:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 19:34 [PATCH for-4.10 0/2] xen/arm: Add more debug in get_page_from_gva Julien Grall
2017-11-15 19:34 ` [PATCH for-4.10 1/2] xen/arm: mm: Change the return value of gvirt_to_maddr Julien Grall
2017-11-16  1:35   ` Stefano Stabellini
2017-11-15 19:34 ` [PATCH for-4.10 2/2] xen/arm: p2m: Add more debug in get_page_from_gva Julien Grall
2017-11-15 19:43   ` Andrew Cooper
2017-11-15 21:42     ` Julien Grall [this message]
2017-11-16  1:36   ` Stefano Stabellini
2017-11-16  8:50     ` Julien Grall
2017-11-16 19:00       ` Stefano Stabellini

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=d25edbc4-85a2-7219-a66a-bde3c15861ee@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=sstabellini@kernel.org \
    --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 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).