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] [PATCH 0/2] enable event channel wake-up for mem_event i

To: Adin Scannell <adin@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/2] enable event channel wake-up for mem_event interfaces
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Fri, 30 Sep 2011 14:09:00 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Tim Deegan <tim@xxxxxxx>
Delivery-date: Fri, 30 Sep 2011 14:09:42 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=ZkCT0BA11ZMzhCo1Ouh39IhPTTCiUpMW/VaP3kPLfxo=; b=JbsX9mBBUGqv+8LYNPXV9ZeReQMIbAKx/fDKYL6KXRQvZOFP+TenYAcrBKWeLl0MiS C2MLBmuzjpZDwaDhIlvpVhU1SSGjVhWaezqYc5qq0nN7cAiHRXXw9N0M6AcTfYnrWu0K Xv2ocBhgBxJJmSXgKlNxRFAl/xq+tKjg1eKvI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAAJKtqoPPzeRZqwERhF_cEey-SVjBMxKk=BwS4FdwS=GhkVp8A@xxxxxxxxxxxxxx>
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: Acx/tSyKAkTdQle0e0ykVtiol05Hgw==
Thread-topic: [Xen-devel] [PATCH 0/2] enable event channel wake-up for mem_event interfaces
User-agent: Microsoft-Entourage/12.30.0.110427
On 30/09/2011 13:57, "Adin Scannell" <adin@xxxxxxxxxxxxxxx> wrote:

>>>> Patch 2/2 I don't mind the principle, but the implementation is not very
>>>> scalable. I will post a rewritten version to the list. It might be early
>>>> next week before I do so.
>>> 
>>> I've attached it. Let me know how it works for you.
> 
> Seems to work for me, thanks!
> 
>> By the way my patch doesn't hook up event notification for the d->mem_share
>> structure. It doesn't look like d->mem_share.xen_port ever gets set up, and
>> your patches didn't appear to fix that either.
> 
> Yeah, it seems that is currently unused (unimplemented). I assume the
> idea was to put OOM notifications (or maybe unshare notifications) in
> that ring.
> 
> Once I hear back on the first patch, I will resend as a series (the
> event mechanism for paging requires the first patch for correctness).

You can put my sign off on the redone second patch when you re-send it:
Signed-off-by: Keir Fraser <keir@xxxxxxx>

Also, most of the reviewers on this list prefer it if you can send patches
in-line in plain text rather than as an attachment. Makes it easier to make
detailed comments.

 -- Keir



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