xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: "Ian Campbell" <Ian.Campbell@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org, tim@xen.org,
	stefano.stabellini@citrix.com
Subject: Re: [PATCH v7 2/4] xen/arm: grant: Add another entry to map MFN 1:1 in dom0 p2m
Date: Tue, 20 May 2014 12:19:39 +0100	[thread overview]
Message-ID: <537B3A4B.7030305@linaro.org> (raw)
In-Reply-To: <1400575900.25175.4.camel@kazak.uk.xensource.com>

On 05/20/2014 09:51 AM, Ian Campbell wrote:
> On Tue, 2014-05-20 at 09:30 +0200, Roger Pau Monné wrote:
>> Not sure I'm following what's going on here, are you saying that FreeBSD
>> blkfront uses the same grant ref on two (or more) requests at the same time?
> 
> My understanding was that there were two grant refs to the same mfn,
> which could happen if two threads were doing (direct?) IO to buffers
> which happened to lie on the same page, or with aio etc.

Sorry I wasn't clear on the use-case.

I'm trying to run portsnap on a FreeBSD ARM guest. The first time I load
the software, the guest is sending (in xbd_queue_cb) at the same time
multiple grant with the same IPA (guest address). This will result to
the same MFN from DOM0/Xen POV.

I did a bit of debug, and this come from the same thread. I have virtual
buffer where each page of this buffer pointed to the same physical address.

FreeBSD is asking to write this buffer to the disk but from what I see
it mostly contains garbage (full of 0xc2).

I can't find where this comes and wondering if you have any thoughts.

I was wondering if this things happen on FreeBSD x86.

Regards,

-- 
Julien Grall

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

  reply	other threads:[~2014-05-20 11:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15 14:16 [PATCH v7 0/4] IOMMU support for ARM Julien Grall
2014-05-15 14:16 ` [PATCH v7 1/4] xen/arm: p2m: Clean cache PT when the IOMMU doesn't support coherent walk Julien Grall
2014-05-15 15:20   ` Ian Campbell
2014-05-15 15:24     ` Julien Grall
2014-05-15 15:51       ` Ian Campbell
2014-05-15 16:05     ` Jan Beulich
2014-05-15 16:04   ` Jan Beulich
2014-05-15 17:06     ` Julien Grall
2014-05-16 10:00       ` Ian Campbell
2014-05-15 14:16 ` [PATCH v7 2/4] xen/arm: grant: Add another entry to map MFN 1:1 in dom0 p2m Julien Grall
2014-05-17 18:12   ` Julien Grall
2014-05-19  9:45     ` Ian Campbell
2014-05-19 14:20       ` Julien Grall
2014-05-20  7:30         ` Roger Pau Monné
2014-05-20  8:51           ` Ian Campbell
2014-05-20 11:19             ` Julien Grall [this message]
2014-05-20 11:25               ` Ian Campbell
2014-05-20 11:53                 ` Julien Grall
2014-05-15 14:16 ` [PATCH v7 3/4] xen: iommu: Define PAGE_{SHIFT, SIZE, ALIGN, MASK)_64K Julien Grall
2014-05-15 14:16 ` [PATCH v7 4/4] drivers/passthrough: arm: Add support for SMMU drivers Julien Grall

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=537B3A4B.7030305@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --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).