From: David Vrabel <david.vrabel@citrix.com>
To: Frediano Ziglio <frediano.ziglio@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: xen: Fix possible page fault in fifo events
Date: Mon, 28 Jul 2014 13:55:04 +0100 [thread overview]
Message-ID: <53D64828.6020209@citrix.com> (raw)
In-Reply-To: <1405432129.1749.5.camel@hamster.uk.xensource.com>
On 15/07/14 14:48, Frediano Ziglio wrote:
> sync_test_bit function require a long* read access to pointer.
> This is a problem if the you are using last entry in the page causing
> an access to next page. If this page is not readable you get a memory
> access failure (page fault).
> All other x64 bit functions access memory using 32 bit operations.
> For processors different than x64 long aligned operations are used.
I think we should implement a set of 32-bit bit ops. We fudged around
it for the arm64 problem but this second problem shows we need a better
solution.
David
next prev parent reply other threads:[~2014-07-28 12:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 13:48 xen: Fix possible page fault in fifo events Frediano Ziglio
2014-07-15 14:32 ` [Xen-devel] " Andrew Cooper
2014-07-15 15:27 ` Konrad Rzeszutek Wilk
2014-07-15 15:27 ` Konrad Rzeszutek Wilk
2014-07-15 15:54 ` [Xen-devel] " Frediano Ziglio
2014-07-15 15:54 ` Frediano Ziglio
2014-07-15 14:32 ` Andrew Cooper
2014-07-28 12:55 ` David Vrabel [this message]
2014-07-28 12:55 ` David Vrabel
-- strict thread matches above, loose matches on Subject: below --
2014-07-15 13:48 Frediano Ziglio
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=53D64828.6020209@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=frediano.ziglio@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.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 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.