linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Juergen Gross <jgross@suse.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	xen-devel@lists.xensource.com, konrad.wilk@oracle.com,
	boris.ostrovsky@oracle.com, tglx@linutronix.de, mingo@redhat.com,
	hpa@zytor.com, mmarek@suse.cz, linux-kbuild@vger.kernel.org
Subject: Re: [Patch V2 0/4] xen: auto-generate symbols for xen hypercalls
Date: Mon, 19 Jan 2015 15:42:28 +0000	[thread overview]
Message-ID: <54BD25E4.3020606@citrix.com> (raw)
In-Reply-To: <54BC9109.50803@suse.com>

On 19/01/15 05:07, Juergen Gross wrote:
> Hi,
> 
> anything missing to take these patches?

Patch #1 needs an x86 maintainer ack.

David

> On 12/17/2014 10:50 AM, Juergen Gross wrote:
>> The Xen hypercalls are defined in include/xen/interface/xen.h. There
>> are some places where for each hypercall a table element is created.
>> Instead of manually add each hypercall element to these tables use
>> an auto generated header built during the make process of the kernel.
>>
>> Changes in V2:
>> - add "autogenerated" comment to generated header file as suggested by
>>    David Vrabel (patch 1)
>> - some minor adjustments to patch 4 as suggested by David Vrabel
>>
>> Juergen Gross (4):
>>    xen: build infrastructure for generating hypercall depending symbols
>>    xen: synchronize include/xen/interface/xen.h with xen
>>    xen: use generated hypervisor symbols in arch/x86/xen/trace.c
>>    xen: use generated hypercall symbols in arch/x86/xen/xen-head.S
>>
>>   arch/x86/syscalls/Makefile  |  9 +++++++
>>   arch/x86/xen/trace.c        | 50 +++--------------------------------
>>   arch/x86/xen/xen-head.S     | 63
>> +++++++--------------------------------------
>>   include/xen/interface/xen.h |  6 ++++-
>>   scripts/xen-hypercalls.sh   | 12 +++++++++
>>   5 files changed, 40 insertions(+), 100 deletions(-)
>>   create mode 100644 scripts/xen-hypercalls.sh
>>
> 


      reply	other threads:[~2015-01-19 15:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17  9:50 [Patch V2 0/4] xen: auto-generate symbols for xen hypercalls Juergen Gross
2014-12-17  9:50 ` [Patch V2 1/4] xen: build infrastructure for generating hypercall depending symbols Juergen Gross
2014-12-17 10:26   ` [Xen-devel] " David Vrabel
2014-12-17  9:50 ` [Patch V2 2/4] xen: synchronize include/xen/interface/xen.h with xen Juergen Gross
2014-12-17  9:50 ` [Patch V2 3/4] xen: use generated hypervisor symbols in arch/x86/xen/trace.c Juergen Gross
2014-12-17  9:50 ` [Patch V2 4/4] xen: use generated hypercall symbols in arch/x86/xen/xen-head.S Juergen Gross
2014-12-17 10:27   ` [Xen-devel] " David Vrabel
2015-01-19  5:07 ` [Patch V2 0/4] xen: auto-generate symbols for xen hypercalls Juergen Gross
2015-01-19 15:42   ` David Vrabel [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=54BD25E4.3020606@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mmarek@suse.cz \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xensource.com \
    /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).