All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@suse.de>
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: behavioral change due to new elf code
Date: Fri, 09 Feb 2007 15:00:30 +0100	[thread overview]
Message-ID: <45CC7E7E.5060607@suse.de> (raw)
In-Reply-To: <45CC86A5.76E4.0078.0@novell.com>

Jan Beulich wrote:
> But wouldn't that change behavior for domU-s then in an undesirable way?

Why?  dom0 and domU should have the same behavior ...

> Even better, I would think, would be to split the note namespace to
> distinguish
> - general required notes
> - general optional notes
> - dom0 required notes

Point being?  I'm not aware of any dom0-required note.  And I don't
think splitting into required and optional is useful, especially as this
is arch-dependent ...

cheers,
  Gerd

-- 
Gerd Hoffmann <kraxel@suse.de>

  reply	other threads:[~2007-02-09 14:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 13:01 behavioral change due to new elf code Jan Beulich
2007-02-09 13:17 ` Gerd Hoffmann
2007-02-09 13:35   ` Jan Beulich
2007-02-09 14:00     ` Gerd Hoffmann [this message]
2007-02-09 14:25       ` Jan Beulich
2007-02-09 14:39         ` Gerd Hoffmann

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=45CC7E7E.5060607@suse.de \
    --to=kraxel@suse.de \
    --cc=jbeulich@novell.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.