[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAB=NE6Xt3QhuKvUm-+-iD4pThsmLZ7oq1nnQbL0Hcw8Q0fpEqw@mail.gmail.com>
Date: Thu, 27 Nov 2014 13:46:34 -0500
From: "Luis R. Rodriguez" <mcgrof@...not-panic.com>
To: Juergen Gross <jgross@...e.com>
Cc: "Luis R. Rodriguez" <mcgrof@...not-panic.com>,
David Vrabel <david.vrabel@...rix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
boris.ostrovsky@...cle.com, xen-devel@...ts.xenproject.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
x86@...nel.org, kvm@...r.kernel.org,
Davidlohr Bueso <dbueso@...e.de>,
Joerg Roedel <jroedel@...e.de>, Borislav Petkov <bp@...e.de>,
Jan Beulich <JBeulich@...e.com>, Olaf Hering <ohering@...e.de>
Subject: Re: [PATCH] xen: privcmd: schedule() after private hypercall when non CONFIG_PREEMPT
On Thu, Nov 27, 2014 at 1:36 PM, Luis R. Rodriguez <mcgrof@...e.com> wrote:
> I'm afraid we don't have much leg room.
Let me be clear, I still think putting some hypercalls in process
context *might help* but because of notes 1) and 2) I highlighted I
think this is the best we can do, with more information we should be
able to consider weighing pros / cons with actual metrics from
alternatives, without more information we're just shooting in the dark
and the last thing I want is to see APIs abused or setting precedents.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists