xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: Borislav Petkov <bp@amd64.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Luck, Tony" <tony.luck@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [Xen-devel] [PATCH 1/3] xen/mce: Add mcelog support for Xen platform (v2)
Date: Fri, 25 May 2012 17:15:24 -0400	[thread overview]
Message-ID: <20120525211524.GC21344@phenom.dumpdata.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC82923351F10DE@SHSMSX101.ccr.corp.intel.com>

On Fri, May 25, 2012 at 08:47:20PM +0000, Liu, Jinsong wrote:
> Konrad Rzeszutek Wilk wrote:
> >> What I mean is,
> >> If mcelog.c create /dev/xen-mcelog (say, minor=226), native mce.c
> >> would create /dev/mcelog (minor=227). 
> >> Under such case, may we create a symlink in /dev/mcelog pointing to
> >> /dev/xen-mcelog, without touching native mce code? and how? 
> > 
> > I thought the idea was that we would create /dev/mcelog using the
> > same major/minor. 
> 
> Our current patch just use same major/minor, by redirection method. Is it acceptable?

https://lkml.org/lkml/2012/5/24/183 Borislav says:
"
Maybe create a symlink in /dev/mcelog pointing to /dev/xen-mcelog?

That should solve it.
" so that sounds like the right direction.

> 
> > 
> > However if you want to create /dev/xen-mcelog and then create from
> > the kernel another file in /dev that is name 'mcelog' and is a
> > symlink to /dev/mcelog - that is OK too. Obviously you will also need
> > to disable the generic '/dev/mcelog' (and that can be done in the
> > same way as lguest does it). 
> 
> No, that's not my purpose.
> 
> Thanks,
> Jinsong

  reply	other threads:[~2012-05-25 21:15 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22  5:45 [PATCH 1/3] xen/mce: Add mcelog support for Xen platform (v2) Liu, Jinsong
2012-05-22  9:23 ` Borislav Petkov
2012-05-24 10:10   ` Liu, Jinsong
2012-05-24 10:30     ` Borislav Petkov
2012-05-24 16:15       ` Liu, Jinsong
2012-05-24 16:26         ` Borislav Petkov
2012-05-24 16:52           ` Liu, Jinsong
2012-05-24 19:10             ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-05-25 18:01               ` Liu, Jinsong
2012-05-25 18:03                 ` Konrad Rzeszutek Wilk
2012-05-25 19:55                   ` Liu, Jinsong
2012-05-25 20:23                     ` Konrad Rzeszutek Wilk
2012-05-25 20:47                       ` Liu, Jinsong
2012-05-25 21:15                         ` Konrad Rzeszutek Wilk [this message]
2012-05-24 18:49         ` Konrad Rzeszutek Wilk
2012-05-25 17:56           ` Liu, Jinsong
2012-05-25 18:01             ` Konrad Rzeszutek Wilk
2012-05-25 18:55               ` Liu, Jinsong
     [not found]               ` <DE8DF0795D48FD4CA783C40EC82923351F0D53@SHSMSX101.ccr.corp.intel.com>
2012-05-28 13:36                 ` Liu, Jinsong
2012-05-29 18:39                   ` Konrad Rzeszutek Wilk
2012-05-30 15:14                     ` Liu, Jinsong
2012-05-28 14:48                 ` [PATCH 1/3] xen/mce: Add mcelog support for Xen platform (RFC) Liu, Jinsong
2012-05-29 13:38                   ` Borislav Petkov
2012-05-29 16:40                     ` Liu, Jinsong
2012-05-29 17:06                       ` Borislav Petkov
2012-05-30 14:40                         ` Liu, Jinsong
2012-05-30 15:09                     ` Liu, Jinsong
2012-05-30 15:08                       ` Konrad Rzeszutek Wilk
2012-05-30 15:20                         ` Liu, Jinsong
2012-05-30 15:29                           ` Borislav Petkov
2012-05-30 17:21                             ` Liu, Jinsong
2012-05-30 17:28                               ` Borislav Petkov
2012-05-31 13:00                             ` Liu, Jinsong

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=20120525211524.GC21344@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=bp@amd64.org \
    --cc=jinsong.liu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).