All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Keir Fraser <keir.xen@gmail.com>,
	Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH] tools/hvmloader: move shared_info to reserved memory area
Date: Thu, 25 Oct 2012 13:46:45 +0200	[thread overview]
Message-ID: <20121025114645.GA7218@aepfle.de> (raw)
In-Reply-To: <CCAE730C.42744%keir.xen@gmail.com>

On Thu, Oct 25, Keir Fraser wrote:

> To be honest, given that the XenPVHVM extensions to Linux won't have been
> tested on such old hypervisors, it wouldn't be a bad thing to bail on
> setting up the extensions when you detect running on a really old Xen
> version (e.g., earlier than 3.4.0) anyway. There's a fair chance of doing
> more harm than good?

I could stick such a check into
arch/x86/xen/enlighten.c:x86_hyper_xen_hvm->detect, by rearranging the
code of xen_hvm_platform and init_hvm_pv_info.  Konrad, what do you
think about that? Recent changes indicate that you did some testing on
3.4 based hosts.

Olaf

  reply	other threads:[~2012-10-25 11:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 17:57 [PATCH] tools/hvmloader: move shared_info to reserved memory area Olaf Hering
2012-10-24 19:05 ` Keir Fraser
2012-10-25  7:42   ` Olaf Hering
2012-10-25  7:51     ` Olaf Hering
2012-10-25 11:33       ` Keir Fraser
2012-10-25 11:39         ` Keir Fraser
2012-10-25 11:46           ` Olaf Hering [this message]
2012-10-25 12:10             ` Ian Campbell
2012-10-25 12:16               ` Olaf Hering
2012-10-26 11:58             ` Konrad Rzeszutek Wilk
2012-10-26 14:08               ` Olaf Hering
2012-10-26 15:51                 ` Olaf Hering
2012-10-26 16:08                   ` Keir Fraser

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=20121025114645.GA7218@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=keir.xen@gmail.com \
    --cc=konrad@kernel.org \
    --cc=xen-devel@lists.xen.org \
    /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.