From: Juergen Gross <jgross@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
x86@kernel.org
Cc: hpa@zytor.com, tglx@linutronix.de, mingo@redhat.com
Subject: Re: [PATCH 0/4] xen: various cleanups
Date: Tue, 7 Aug 2018 17:21:01 +0200 [thread overview]
Message-ID: <83652e26-812d-8b2a-91b1-eb87b589243e@suse.com> (raw)
In-Reply-To: <de59d247-7745-bdf2-948a-03170af3b526@oracle.com>
On 07/08/18 16:00, Boris Ostrovsky wrote:
> On 08/07/2018 09:10 AM, Juergen Gross wrote:
>> On 17/07/18 14:01, Juergen Gross wrote:
>>> Some Xen related cleanups:
>>> - move some pv-only code from CONFIG_XEN to CONFIG_XEN_PV
>>> - use CONFIG_XEN_PVHVM in Makefile instead of #ifdef around a complete source
>>> - add SPDX identifier where missing
>>>
>>> Juergen Gross (4):
>>> xen: move pv irq related functions under CONFIG_XEN_PV umbrella
>>> xen: move pv specific parts of arch/x86/xen/mmu.c to mmu_pv.c
>>> xen: link platform-pci-unplug.o only if CONFIG_XEN_PVHVM
>>> xen: add SPDX identifier in arch/x86/xen files
>>>
>>> arch/x86/entry/entry_32.S | 8 +-
>>> arch/x86/entry/entry_64.S | 8 +-
>>> arch/x86/xen/Makefile | 41 ++++++--
>>> arch/x86/xen/efi.c | 14 +--
>>> arch/x86/xen/enlighten.c | 2 +
>>> arch/x86/xen/enlighten_hvm.c | 2 +
>>> arch/x86/xen/grant-table.c | 25 +----
>>> arch/x86/xen/mmu.c | 188 +------------------------------------
>>> arch/x86/xen/mmu_pv.c | 140 +++++++++++++++++++++++++++
>>> arch/x86/xen/p2m.c | 2 +
>>> arch/x86/xen/pci-swiotlb-xen.c | 2 +
>>> arch/x86/xen/platform-pci-unplug.c | 18 +---
>>> arch/x86/xen/vdso.h | 2 +
>>> arch/x86/xen/xen-pvh.S | 15 +--
>>> include/xen/interface/memory.h | 6 --
>>> include/xen/xen-ops.h | 133 +++++++++++++++++---------
>>> 16 files changed, 287 insertions(+), 319 deletions(-)
>>>
>> Boris, any objections?
>
>
> This series had my R-b, but I was waiting for x86 maintainers to ack the
> first patch.
>
> But now that I looked at this again, I wonder whether
>
> +#ifdef CONFIG_XEN
> BUILD_INTERRUPT3(xen_hvm_callback_vector, HYPERVISOR_CALLBACK_VECTOR,
> xen_evtchn_do_upcall)
> +#endif
>
>
> and
>
> +#ifdef CONFIG_XEN
> apicinterrupt3 HYPERVISOR_CALLBACK_VECTOR \
> xen_hvm_callback_vector xen_evtchn_do_upcall
> +#endif
>
>
> should be under XEN_PVHVM
Hmm, right. Do you want to change that while committing or should I send
V2?
Juergen
next prev parent reply other threads:[~2018-08-07 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 12:01 Juergen Gross
2018-07-17 12:01 ` [PATCH 1/4] xen: move pv irq related functions under CONFIG_XEN_PV umbrella Juergen Gross
2018-07-17 19:19 ` Boris Ostrovsky
2018-07-18 4:57 ` Juergen Gross
2018-07-17 12:01 ` [PATCH 2/4] xen: move pv specific parts of arch/x86/xen/mmu.c to mmu_pv.c Juergen Gross
2018-07-17 12:01 ` [PATCH 3/4] xen: link platform-pci-unplug.o only if CONFIG_XEN_PVHVM Juergen Gross
2018-07-17 12:01 ` [PATCH 4/4] xen: add SPDX identifier in arch/x86/xen files Juergen Gross
2018-08-07 13:10 ` [PATCH 0/4] xen: various cleanups Juergen Gross
2018-08-07 14:00 ` Boris Ostrovsky
2018-08-07 15:21 ` Juergen Gross [this message]
2018-08-07 16:43 ` Boris Ostrovsky
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=83652e26-812d-8b2a-91b1-eb87b589243e@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®