All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [HYBRID]: XEN_EMULATE_PREFIX in user process
Date: Fri, 29 Jun 2012 23:04:14 +0100	[thread overview]
Message-ID: <1341007454.5953.18.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <20120629120738.425781e5@mantra.us.oracle.com>

On Fri, 2012-06-29 at 20:07 +0100, Mukesh Rathor wrote:
> On Fri, 29 Jun 2012 11:15:46 -0700
> Mukesh Rathor <mukesh.rathor@oracle.com> wrote:
> > > It's unlikely but not impossible for a userspace developer to have
> > > done some "Xen magic" and used the prefix in userspace.
> > > 
> > > What version of dm_mapper do you have? I checked the version in
> > > Debian Sid and it doesn't do this (at least not directly).
> > > 
> > > Are you able to run the dm_mapper process under gdb and inspect it
> > > to find the prefix?
> > 
> > Well, let me take that back. dm_mapper is the last printk, but it
> > could be anything after that or that. 
> > 
> > Unfortunately, it's dom0 and during boot, so can't run gdb on it. I am
> > hacking the kernel now to print every user process name in schedule.
> 
> Ah, it's "xen-detect" coming in right after dm_mapper. I see the
> xen prefix in it. Hmm... let me see if I can add some run time check
> for hybrid dom0, then won't have to worry about invalid_op trap. Less
> code that way. That's the end goal anyways...

I don't think reducing code should come at the expense of adding special
cases for hybrid to userspace programs...

I think you'll have to handle the invalid op, it can't be that much
code, can it?

Ian

  reply	other threads:[~2012-06-29 22:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29  1:00 [HYBRID]: XEN_EMULATE_PREFIX in user process Mukesh Rathor
2012-06-29  1:09 ` Konrad Rzeszutek Wilk
2012-06-29  1:26   ` Mukesh Rathor
2012-06-29  8:09     ` Ian Campbell
2012-06-29 18:15       ` Mukesh Rathor
2012-06-29 19:07         ` Mukesh Rathor
2012-06-29 22:04           ` Ian Campbell [this message]
2012-06-29 22:50             ` Mukesh Rathor
2012-07-02  8:27               ` Jan Beulich
2012-07-02  9:29                 ` Ian Campbell
2012-07-02 18:18                 ` Mukesh Rathor
2012-06-29  7:56 ` Jan Beulich
2012-06-29  8:07   ` Ian Campbell
2012-06-29  8:15     ` Jan Beulich
2012-06-29 21:18   ` Mukesh Rathor

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=1341007454.5953.18.camel@dagon.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=Xen-devel@lists.xensource.com \
    --cc=konrad.wilk@oracle.com \
    --cc=mukesh.rathor@oracle.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.