From: Jan Beulich <jbeulich@suse.com>
To: Wei Liu <wl@xen.org>
Cc: "Wei Liu" <liuwe@microsoft.com>, "Paul Durrant" <paul@xen.org>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Michael Kelley" <mikelley@microsoft.com>,
"Xen Development List" <xen-devel@lists.xenproject.org>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH v4 5/7] x86/hyperv: provide percpu hypercall input page
Date: Thu, 23 Jan 2020 16:45:38 +0100 [thread overview]
Message-ID: <e72f37cf-63cb-9c10-00e2-96f946208265@suse.com> (raw)
In-Reply-To: <20200122202343.5703-6-liuwe@microsoft.com>
On 22.01.2020 21:23, Wei Liu wrote:
> --- a/xen/arch/x86/guest/hyperv/hyperv.c
> +++ b/xen/arch/x86/guest/hyperv/hyperv.c
> @@ -27,7 +27,10 @@
> #include <asm/guest/hyperv-tlfs.h>
> #include <asm/processor.h>
>
> +#include "private.h"
> +
> struct ms_hyperv_info __read_mostly ms_hyperv;
> +DEFINE_PER_CPU_READ_MOSTLY(void *, hv_pcpu_input_arg);
Would it perhaps be helpful to make recognizable that this can hold
up to a page's worth of data, either by its type or by a slightly
different name?
> @@ -119,14 +122,36 @@ static void __init setup_hypercall_page(void)
> }
> }
>
> +static void setup_hypercall_pcpu_arg(void)
> +{
> + void *mapping;
> +
> + if ( this_cpu(hv_pcpu_input_arg) )
> + return;
> +
> + mapping = alloc_xenheap_page();
> + if ( !mapping )
> + panic("Failed to allocate hypercall input page for CPU%u\n",
> + smp_processor_id());
panic() is likely fine for the BSP, but I don't think any AP should
be able to bring down the system because of memory shortage. Such
an AP should simply not come online. (Even for the BSP the question
is whether Xen would be able to run despite failure here.)
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-01-23 15:45 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 20:23 [Xen-devel] [PATCH v4 0/7] More Hyper-V infrastructure Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 1/7] x86: provide executable fixmap facility Wei Liu
2020-01-22 20:56 ` Andrew Cooper
2020-01-28 15:09 ` Wei Liu
2020-01-23 11:04 ` Jan Beulich
2020-01-28 15:15 ` Wei Liu
2020-01-28 15:38 ` Jan Beulich
2020-01-29 14:42 ` Wei Liu
2020-01-29 14:59 ` Jan Beulich
2020-01-29 16:37 ` Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 2/7] x86/hyperv: setup hypercall page Wei Liu
2020-01-22 21:31 ` Andrew Cooper
2020-01-23 10:04 ` Jan Beulich
2020-01-28 15:19 ` Wei Liu
2020-01-23 1:35 ` Michael Kelley
2020-01-28 15:20 ` Wei Liu
2020-01-23 11:18 ` Jan Beulich
2020-01-23 15:20 ` Michael Kelley
2020-01-28 15:30 ` Wei Liu
2020-01-28 15:41 ` Jan Beulich
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 3/7] x86/hyperv: provide Hyper-V hypercall functions Wei Liu
2020-01-22 21:57 ` Andrew Cooper
2020-01-23 10:13 ` Jan Beulich
2020-01-29 18:25 ` Wei Liu
2020-01-23 11:28 ` Jan Beulich
2020-01-29 18:37 ` Wei Liu
2020-01-30 8:12 ` Jan Beulich
2020-01-30 11:55 ` Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 4/7] DO NOT APPLY: x86/hyperv: issue an hypercall Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 5/7] x86/hyperv: provide percpu hypercall input page Wei Liu
2020-01-23 15:45 ` Jan Beulich [this message]
2020-01-28 15:50 ` Wei Liu
2020-01-28 16:15 ` Jan Beulich
2020-01-28 16:52 ` Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 6/7] x86/hyperv: retrieve vp_index from Hyper-V Wei Liu
2020-01-23 15:48 ` Jan Beulich
2020-01-28 15:55 ` Wei Liu
2020-01-28 16:18 ` Jan Beulich
2020-01-28 16:33 ` Durrant, Paul
2020-01-28 16:53 ` Wei Liu
2020-01-28 17:01 ` Durrant, Paul
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 7/7] x86/hyperv: setup VP assist page Wei Liu
2020-01-22 22:05 ` Andrew Cooper
2020-01-23 15:50 ` Jan Beulich
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=e72f37cf-63cb-9c10-00e2-96f946208265@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=liuwe@microsoft.com \
--cc=mikelley@microsoft.com \
--cc=paul@xen.org \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 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).