From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] arm: fix build after c/s 25477:e12e0b038219
Date: Thu, 28 Jun 2012 14:53:12 +0100 [thread overview]
Message-ID: <CC122058.44500%keir@xen.org> (raw)
In-Reply-To: <4FEC7460020000780008C821@nat28.tlf.novell.com>
On 28/06/2012 14:12, "Jan Beulich" <JBeulich@suse.com> wrote:
>>>> On 28.06.12 at 15:03, Keir Fraser <keir@xen.org> wrote:
>> On 25/06/2012 11:54, "Jan Beulich" <JBeulich@suse.com> wrote:
>>
>>> Only x86 currently has a struct vcpu field arch.gdbsx_vcpu_event. But
>>> as the whole function domain_pause_for_debugger() is pointless to be
>>> compiled when there's no arch support, simply introduce another HAS_*
>>> macro, enabled only on x86.
>>>
>>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>>
>> How did arch/arm build at all then, previously, with this function present
>> for a long time in common code?
>
> Prior to said c/s adding a reference to ->arch.gdbsx_vcpu_event,
> the function wasn't arch-specific at all.
Ah yes, of course. :)
>> Would a better fix be just to move the
>> function to arch/x86/domain.c, since it is only called by arch/x86?
>
> I'd say no - the function really ought to be generic. Any arch
> wanting gdbsx support would have to add a respective field to
> its arch_vcpu. Or alternatively the field itself should get moved
> into struct vcpu, perhaps dependent upon some CONFIG_*.
> (This is also why I didn't want to put in e.g. a CONFIG_X86
> conditional, which would have been a smaller change.)
Well, fine then.
Acked-by: Keir Fraser <keir@xen.org>
> Jan
>
>>> --- a/xen/Rules.mk
>>> +++ b/xen/Rules.mk
>>> @@ -51,6 +51,7 @@ CFLAGS-$(perfc) += -DPERF_COUNTE
>>> CFLAGS-$(perfc_arrays) += -DPERF_ARRAYS
>>> CFLAGS-$(lock_profile) += -DLOCK_PROFILE
>>> CFLAGS-$(HAS_ACPI) += -DHAS_ACPI
>>> +CFLAGS-$(HAS_GDBSX) += -DHAS_GDBSX
>>> CFLAGS-$(HAS_PASSTHROUGH) += -DHAS_PASSTHROUGH
>>> CFLAGS-$(frame_pointer) += -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER
>>>
>>> --- a/xen/arch/x86/Rules.mk
>>> +++ b/xen/arch/x86/Rules.mk
>>> @@ -9,6 +9,7 @@ HAS_PASSTHROUGH := y
>>> HAS_NS16550 := y
>>> HAS_EHCI := y
>>> HAS_KEXEC := y
>>> +HAS_GDBSX := y
>>> xenoprof := y
>>>
>>> #
>>> --- a/xen/common/domain.c
>>> +++ b/xen/common/domain.c
>>> @@ -612,6 +612,7 @@ void vcpu_end_shutdown_deferral(struct v
>>> vcpu_check_shutdown(v);
>>> }
>>>
>>> +#ifdef HAS_GDBSX
>>> void domain_pause_for_debugger(void)
>>> {
>>> struct domain *d = current->domain;
>>> @@ -628,6 +629,7 @@ void domain_pause_for_debugger(void)
>>> if (current->arch.gdbsx_vcpu_event == 0)
>>> send_global_virq(VIRQ_DEBUGGER);
>>> }
>>> +#endif
>>>
>>> /* Complete domain destroy after RCU readers are not holding old
>> references.
>>> */
>>> static void complete_domain_destroy(struct rcu_head *head)
>>>
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xen.org
>>> http://lists.xen.org/xen-devel
>
>
>
prev parent reply other threads:[~2012-06-28 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 10:54 [PATCH] arm: fix build after c/s 25477:e12e0b038219 Jan Beulich
2012-06-25 11:05 ` Ian Campbell
2012-06-26 15:15 ` Jan Beulich
2012-06-28 13:03 ` Keir Fraser
2012-06-28 13:12 ` Jan Beulich
2012-06-28 13:53 ` Keir Fraser [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=CC122058.44500%keir@xen.org \
--to=keir@xen.org \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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).