Hi Keir
Thanks for your comments.
My modification is a simple reading interface that is independent
from the interface of "xc_readconsolering (clear/non-clear)"
that xm dmesg uses. It can be used if "clear" argument is
a negative value.
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.
- modification to give the responsibility of logging of the message
 to only one daemon. Other commands and daemons must read
 the logging file never to issue xc_readconsolering().
best regards,
Katsuhito Minai
On 2006年 7月月 11日 (火) 12:00 am, Keir Fraser said:
>
> On 7 Jul 2006, at 09:17, MINAI Katsuhito wrote:
>
>> [1/4] add read pointer to the xen console ring
>>
>> Signed-off-by: Katsuhito Minai <minai@xxxxxxxxxxxxxx>
>
> Can you briefly explain the semantics of the modified console
> interface. I'd rather change the interface cleanly than abuse the
> 'clear' field -- we've broken dom0_op compatibility since 3.0.2 anyway,
> so taking the cleaner route is definitely preferable.
>
> -- Keir
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel