WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: how to handle paged hypercall args?

To: Jan Beulich <JBeulich@xxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: how to handle paged hypercall args?
From: Keir Fraser <keir@xxxxxxx>
Date: Mon, 15 Nov 2010 10:09:37 +0000
Cc: Olaf Hering <olaf@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Patrick Colp <pjcolp@xxxxxxxxx>
Delivery-date: Mon, 15 Nov 2010 02:10:41 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:user-agent:date :subject:from:to:cc:message-id:thread-topic:thread-index:in-reply-to :mime-version:content-type:content-transfer-encoding; bh=I9mEzvXWIZuTsT6c7a8c4KlhsL3EQYGsENt+MUdP07g=; b=jXHrmuLGPPKdlE6PQDqI/Knzns+EUJL5XiO9qo8BE58hEzPS5lPSM/FEqYwjXk6mpu HG4EeFesRsUIuzNjeWsFaQzUQ8eZ/+YMb/j7luwtDGPdRrBILZK0n3sZ9YDowRm4zlo/ 7HdTANzN7/W7vxuvTX2a9TOP/CLeLmfPHopP0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=sBDEGdfRqf5t7D7o5eHlhwXl3JtcfbrQx1aCHZ1igGTWNMU+0wuZYAIEE4Kx4jyJcD j0acjwf+UjoTbTnzXqBdokk547jRwysvWW3qPV8qGYvG+cCjWDqafqaLqyoCRDlY7Iwb ua7tVULAaNUOOE7+CnDNti1dtTWpXNXOUvw0I=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CE111470200007800022344@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcuErTVhlex0deV9p06ujpSFBCDmLQ==
Thread-topic: [Xen-devel] Re: how to handle paged hypercall args?
User-agent: Microsoft-Entourage/12.27.0.100910
On 15/11/2010 09:53, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:

>> Maybe Patrick can comment too, but my recollection of discussing this is
>> that we would have to propagate failures caused by paging at least as
>> far as the dom0 kernel, because otherwise a single-vcpu dom0 kernel
>> could deadlock with its one vcpu stuck in a hypercall (or continually
>> having it preempted and retried) and the paging binary that would
>> unstick it never getting scheduled.
> 
> How's Dom0 involved here? The hypercall arguments live in
> guest memory.

Yes, and you'd never turn on paging for dom0 itself. That would never work!

Changing every user of the guest accessor macros to retry via guest space is
really not tenable. We'd never get all the bugs out.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel