From: Juergen Gross <jgross@suse.com>
To: Ankur Arora <ankur.a.arora@oracle.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: pbonzini@redhat.com, boris.ostrovsky@oracle.com,
konrad.wilk@oracle.com, sstabellini@kernel.org,
joao.m.martins@oracle.com
Subject: Re: [RFC PATCH 08/16] x86/xen: irq/upcall handling with multiple xenhosts
Date: Fri, 14 Jun 2019 14:01:14 +0200 [thread overview]
Message-ID: <7eb08024-73c8-ef1f-cacc-e5105102c28d@suse.com> (raw)
In-Reply-To: <20190509172540.12398-9-ankur.a.arora@oracle.com>
On 09.05.19 19:25, Ankur Arora wrote:
> For configurations with multiple xenhosts, we need to handle events
> generated from multiple xenhosts.
>
> Having more than one upcall handler might be quite hairy, and it would
> be simpler if the callback from L0-Xen could be bounced via L1-Xen.
> This will also mean simpler pv_irq_ops code because now the IF flag
> maps onto the xh_default->vcpu_info->evtchn_upcall_mask.
>
> However, we still update the xh_remote->vcpu_info->evtchn_upcall_mask
> on a best effort basis to minimize unnecessary work in remote xenhost.
This is another design decision yet to be taken.
My current prefernce is L1 Xen mapping events from L0 to L1 guest
events.
Juergen
WARNING: multiple messages have this Message-ID (diff)
From: Juergen Gross <jgross@suse.com>
To: Ankur Arora <ankur.a.arora@oracle.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: pbonzini@redhat.com, boris.ostrovsky@oracle.com,
sstabellini@kernel.org, joao.m.martins@oracle.com,
konrad.wilk@oracle.com
Subject: Re: [Xen-devel] [RFC PATCH 08/16] x86/xen: irq/upcall handling with multiple xenhosts
Date: Fri, 14 Jun 2019 14:01:14 +0200 [thread overview]
Message-ID: <7eb08024-73c8-ef1f-cacc-e5105102c28d@suse.com> (raw)
In-Reply-To: <20190509172540.12398-9-ankur.a.arora@oracle.com>
On 09.05.19 19:25, Ankur Arora wrote:
> For configurations with multiple xenhosts, we need to handle events
> generated from multiple xenhosts.
>
> Having more than one upcall handler might be quite hairy, and it would
> be simpler if the callback from L0-Xen could be bounced via L1-Xen.
> This will also mean simpler pv_irq_ops code because now the IF flag
> maps onto the xh_default->vcpu_info->evtchn_upcall_mask.
>
> However, we still update the xh_remote->vcpu_info->evtchn_upcall_mask
> on a best effort basis to minimize unnecessary work in remote xenhost.
This is another design decision yet to be taken.
My current prefernce is L1 Xen mapping events from L0 to L1 guest
events.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-06-14 12:01 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 17:25 [RFC PATCH 00/16] xenhost support Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` [RFC PATCH 01/16] x86/xen: add xenhost_t interface Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-06-07 15:04 ` Juergen Gross
2019-06-07 15:04 ` [Xen-devel] " Juergen Gross
2019-06-11 7:16 ` Ankur Arora
2019-06-11 7:16 ` [Xen-devel] " Ankur Arora
2019-06-14 11:52 ` Juergen Gross
2019-06-14 11:52 ` [Xen-devel] " Juergen Gross
2019-05-09 17:25 ` Ankur Arora
2019-05-09 17:25 ` [RFC PATCH 02/16] x86/xen: cpuid support in xenhost_t Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-06-12 21:09 ` [Xen-devel] " Andrew Cooper
2019-06-12 21:09 ` Andrew Cooper
2019-05-09 17:25 ` [RFC PATCH 03/16] x86/xen: make hypercall_page generic Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-05-09 17:25 ` [RFC PATCH 04/16] x86/xen: hypercall support for xenhost_t Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-06-12 21:15 ` Andrew Cooper
2019-06-12 21:15 ` Andrew Cooper
2019-06-14 7:20 ` Ankur Arora
2019-06-14 7:20 ` Ankur Arora
2019-06-14 7:35 ` Juergen Gross
2019-06-14 7:35 ` Juergen Gross
2019-06-14 8:00 ` Andrew Cooper
2019-06-14 8:00 ` Andrew Cooper
2019-05-09 17:25 ` [RFC PATCH 05/16] x86/xen: add feature support in xenhost_t Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` [RFC PATCH 06/16] x86/xen: add shared_info support to xenhost_t Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-06-07 15:08 ` Juergen Gross
2019-06-07 15:08 ` [Xen-devel] " Juergen Gross
2019-06-08 5:01 ` Ankur Arora
2019-06-08 5:01 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-05-09 17:25 ` [RFC PATCH 07/16] x86/xen: make vcpu_info part of xenhost_t Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-06-14 11:53 ` Juergen Gross
2019-06-14 11:53 ` [Xen-devel] " Juergen Gross
2019-06-17 6:28 ` Ankur Arora
2019-06-17 6:28 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` [RFC PATCH 08/16] x86/xen: irq/upcall handling with multiple xenhosts Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-06-14 12:01 ` Juergen Gross [this message]
2019-06-14 12:01 ` Juergen Gross
2019-05-09 17:25 ` [RFC PATCH 09/16] xen/evtchn: support evtchn in xenhost_t Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-06-14 12:04 ` Juergen Gross
2019-06-14 12:04 ` [Xen-devel] " Juergen Gross
2019-06-17 6:09 ` Ankur Arora
2019-06-17 6:09 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-05-09 17:25 ` [RFC PATCH 10/16] xen/balloon: support ballooning " Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-06-17 9:28 ` Juergen Gross
2019-06-17 9:28 ` [Xen-devel] " Juergen Gross
2019-06-19 2:24 ` Ankur Arora
2019-06-19 2:24 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` [RFC PATCH 11/16] xen/grant-table: make grant-table xenhost aware Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-06-17 9:36 ` Juergen Gross
2019-06-17 9:36 ` [Xen-devel] " Juergen Gross
2019-06-19 2:25 ` Ankur Arora
2019-06-19 2:25 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` [RFC PATCH 12/16] xen/xenbus: support xenbus frontend/backend with xenhost_t Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-06-17 9:50 ` Juergen Gross
2019-06-17 9:50 ` [Xen-devel] " Juergen Gross
2019-06-19 2:38 ` Ankur Arora
2019-06-19 2:38 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` [RFC PATCH 13/16] drivers/xen: gnttab, evtchn, xenbus API changes Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-06-17 10:07 ` Juergen Gross
2019-06-17 10:07 ` [Xen-devel] " Juergen Gross
2019-06-19 2:55 ` Ankur Arora
2019-06-19 2:55 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-05-09 17:25 ` [RFC PATCH 14/16] xen/blk: " Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-06-17 10:14 ` Juergen Gross
2019-06-17 10:14 ` [Xen-devel] " Juergen Gross
2019-06-19 2:59 ` Ankur Arora
2019-06-19 2:59 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-05-09 17:25 ` [RFC PATCH 15/16] xen/net: " Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-06-17 10:14 ` Juergen Gross
2019-06-17 10:14 ` [Xen-devel] " Juergen Gross
2019-05-09 17:25 ` [RFC PATCH 16/16] xen/grant-table: host_addr fixup in mapping on xenhost_r0 Ankur Arora
2019-05-09 17:25 ` [Xen-devel] " Ankur Arora
2019-06-17 10:55 ` Juergen Gross
2019-06-17 10:55 ` [Xen-devel] " Juergen Gross
2019-06-19 3:02 ` Ankur Arora
2019-06-19 3:02 ` [Xen-devel] " Ankur Arora
2019-05-09 17:25 ` Ankur Arora
2019-06-07 14:51 ` [RFC PATCH 00/16] xenhost support Juergen Gross
2019-06-07 14:51 ` [Xen-devel] " Juergen Gross
2019-06-07 15:22 ` Joao Martins
2019-06-07 15:22 ` [Xen-devel] " Joao Martins
2019-06-07 16:21 ` Juergen Gross
2019-06-07 16:21 ` [Xen-devel] " Juergen Gross
2019-06-08 5:50 ` Ankur Arora
2019-06-08 5:50 ` Ankur Arora
2019-06-08 5:33 ` Ankur Arora
2019-06-08 5:33 ` [Xen-devel] " Ankur Arora
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=7eb08024-73c8-ef1f-cacc-e5105102c28d@suse.com \
--to=jgross@suse.com \
--cc=ankur.a.arora@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=joao.m.martins@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sstabellini@kernel.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 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.