All of lore.kernel.org
 help / color / mirror / Atom feed
From: MINAI Katsuhito <minai@jp.fujitsu.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] [0/5] put xen console message into syslog
Date: Fri, 20 Oct 2006 21:44:40 +0900	[thread overview]
Message-ID: <20061020201210.C2DA.MINAI@jp.fujitsu.com> (raw)

Hi Keir,

I am sorry for the delayed response.  
This is the patch reflecting yourI'd like to post the patch 
that reflects your advice in the mail below.

http://lists.xensource.com/archives/html/xen-devel/2006-07/msg00307.html

It becomes possible to put Xen console message into syslog 
and to know the time stamp. 

> Yes, that is an out-of-range input index gets 'rounded up' to the first 
> in-range index. I think that seems a sensible method for bootstrapping 
> a caller with no knowledge about current ring indexes -- they'd pass 
> zero as input and then get back information about the first valid 
> index. Another way would be to have an input flag or unique input index 
> value that means 'just get me characters from the first valid index'. I 
> somewhat prefer the method I already described though.

You are right.  
If the index that specified by the caller program is older than 
the oldest readable character index, Xen returns the current oldest index 
in this patch.

The policy of the change is as follows. 
1. The existing library interface is not changed 
   except "xen_sysctl_readconsole" structure. 
2. A new library interface is designed to hand over the index managed by
   the program that reads console messages. 
3. "xen_sysctl_readconsole" structure is changed as follows: 
    - The type of "clear" menber is moved to int32_t.
    - "cindex" member is added.


Signed-off-by: Katsuhito Minai <minai@jp.fujitsu.com>

Best Regards,
Katsuhito Minai

                 reply	other threads:[~2006-10-20 12:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061020201210.C2DA.MINAI@jp.fujitsu.com \
    --to=minai@jp.fujitsu.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.