From: Andrew Morton <akpm@linux-foundation.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, gleb@redhat.com,
pbonzini@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH 01/14] asmlinkage, kvm: Make kvm_rebooting visible
Date: Mon, 10 Feb 2014 15:46:37 -0800 [thread overview]
Message-ID: <20140210154637.dd58edfcbae273034d34c4df@linux-foundation.org> (raw)
In-Reply-To: <1391845930-28580-1-git-send-email-ak@linux.intel.com>
On Sat, 8 Feb 2014 08:51:57 +0100 Andi Kleen <ak@linux.intel.com> wrote:
> kvm_rebooting is referenced from assembler code, thus
> needs to be visible.
So I read the gcc page and looked at the __visible definition but I
still don't really get it. What goes wrong if the __visible isn't
present on these referenced-from-asm identifiers?
> Cc: gleb@redhat.com
> Cc: pbonzini@redhat.com
Grumble. Email addresses go into commits with display names and <>.
At least, 89.3% of them do. Some sucker has to go through these and
fix them up. I'd prefer it not be me ;)
>
> ...
>
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -102,7 +102,7 @@ static void kvm_release_pfn_dirty(pfn_t pfn);
> static void mark_page_dirty_in_slot(struct kvm *kvm,
> struct kvm_memory_slot *memslot, gfn_t gfn);
>
> -bool kvm_rebooting;
> +__visible bool kvm_rebooting;
> EXPORT_SYMBOL_GPL(kvm_rebooting);
>
> static bool largepages_enabled = true;
prev parent reply other threads:[~2014-02-10 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 7:51 [PATCH 01/14] asmlinkage, kvm: Make kvm_rebooting visible Andi Kleen
2014-02-08 8:13 ` Paolo Bonzini
2014-02-10 23:46 ` Andrew Morton [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=20140210154637.dd58edfcbae273034d34c4df@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@linux.intel.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=x86@kernel.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