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] [1/4] put xen console message into syslog but xm

To: "MINAI Katsuhito" <minai@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] [1/4] put xen console message into syslog but xm dmesg is not affected
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 11 Jul 2006 07:42:12 +0100
Cc: Mark Williamson <mark.williamson@xxxxxxxxxxxx>, Hans-Christian Armingeon <mog.johnny@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>
Delivery-date: Mon, 10 Jul 2006 23:49:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1202.10.34.178.216.1152581316.squirrel@xxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20060707170404.E3CC.MINAI@xxxxxxxxxxxxxx> <8f6c63685e997067f1bf7a39d9372c64@xxxxxxxxxxxx> <1202.10.34.178.216.1152581316.squirrel@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 11 Jul 2006, at 02:28, MINAI Katsuhito wrote:

However, I also think that the "clear" interface is unnecessary.
I think that better solution is one of the following idea:
- modification to have independent read pointer of the buffer
  for each commands and daemons just like reading usual file.
  But, this might be difficult for hypervisor.

Yes, this would be good. The caller could pass a start index and a length. Xen then returns characters from that index, up to length bytes (if available). If the given index is too far behind Xen's producer index, Xen would provide bytes from index position (producer - ring_size). In either case Xen would return index position of first byte returned.

 -- Keir


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