From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH] x86/pv: Prune include lists
Date: Tue, 5 May 2020 15:51:53 +0200 [thread overview]
Message-ID: <460a0a7a-17b4-5f02-943d-4b637d2a089c@suse.com> (raw)
In-Reply-To: <20200505114236.31269-1-andrew.cooper3@citrix.com>
On 05.05.2020 13:42, Andrew Cooper wrote:
> Several of these in particular haven't been pruned since the logic was all
> part of arch/x86/traps.c
>
> Some adjustments to header files are required to avoid compile errors:
> * emulate.h needs xen/sched.h because gdt_ldt_desc_ptr() uses v->vcpu_id.
> * mmconfig.h needs to forward declare acpi_table_header.
> * shadow.h and trace.h need to have uint*_t in scope before including the Xen
> public headers. For shadow.h, reorder the includes. For trace.h, include
> types.h
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
prev parent reply other threads:[~2020-05-05 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 11:42 [PATCH] x86/pv: Prune include lists Andrew Cooper
2020-05-05 13:51 ` Jan Beulich [this message]
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=460a0a7a-17b4-5f02-943d-4b637d2a089c@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--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 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.