All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0/5] x86: properly propagate errors to hypercall callee
Date: Fri, 11 Mar 2011 12:33:27 +0000	[thread overview]
Message-ID: <C99FC717.149AD%keir.xen@gmail.com> (raw)
In-Reply-To: <4D7A0B120200007800035CB4@vpn.id2.novell.com>

On 11/03/2011 10:44, "Jan Beulich" <JBeulich@novell.com> wrote:

> ioremap() in general can fail, but failure of the writing the page
> table entries gets propagated to the caller only on the legacy
> kernels iirc (due to the lack of a return value of the accessor for
> pv-ops).
> 
> The problem at hand, however, is with the vm_insert_...()
> functions, which use set_pte_at(), which again has no return
> value, so it'll need to be the accessors themselves to
> 
> (a) never utilize the writeable page tables feature on any path
> that can alter cache attributes, and
> 
> (b) handle -ENOMEM from HYPERVISOR_update_va_mapping()
> and HYPERVISOR_mmu_update() (without knowing much about
> the context they're being called in).

I can't see changes like that getting upstream. Maybe okay if you're
prepared to carry the patch. Also I guess some callers may have trouble
handling the error no matter how far you punt it up the call chain.

 -- Keir

  reply	other threads:[~2011-03-11 12:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 10:53 [PATCH 0/5] x86: properly propagate errors to hypercall callee Jan Beulich
2011-03-09 11:07 ` Keir Fraser
2011-03-09 11:21   ` Jan Beulich
2011-03-09 13:44     ` Keir Fraser
2011-03-09 14:20       ` Jan Beulich
2011-03-09 15:10         ` Konrad Rzeszutek Wilk
2011-03-09 15:40           ` Jan Beulich
2011-03-11  9:25   ` Jan Beulich
2011-03-11  9:45     ` Keir Fraser
2011-03-11 10:44       ` Jan Beulich
2011-03-11 12:33         ` Keir Fraser [this message]
2011-03-15 12:29 ` Jan Beulich

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=C99FC717.149AD%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=JBeulich@novell.com \
    --cc=xen-devel@lists.xensource.com \
    /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.