From: Christoph Egger <Christoph.Egger@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] MCE: support cpu notification chain
Date: Fri, 26 Oct 2012 10:24:23 +0200 [thread overview]
Message-ID: <508A48B7.8050201@amd.com> (raw)
In-Reply-To: <50896F5D02000078000A4991@nat28.tlf.novell.com>
On 10/25/12 16:57, Jan Beulich wrote:
>>>> On 25.10.12 at 16:45, Christoph Egger <Christoph.Egger@amd.com> wrote:
>> On 10/25/12 16:18, Christoph Egger wrote:
>>> On 10/25/12 16:10, Jan Beulich wrote:
>>>>>>> On 25.10.12 at 15:54, Christoph Egger <Christoph.Egger@amd.com> wrote:
>>>>> Add support for cpu notification chain.
>>>>> This is useful with nested virtualization when Xen
>>>>> runs as l1 hypervisor.
>>>>> This cleans up mce initialization cleanup as a side-effect.
>>>>
>>>> Did you notice the fix I had done to your earlier patch before
>>>> committing c/s 26106:1883c1d29de9? With the change here,
>>>> mce_clear_banks will get allocated twice (once in generic code
>>>> and once in AMD specific code), leaking one instance.
>>>
>>> Ugh... must be a merge botch.
>>
>> Updated patch attached.
>>
>> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
>
> Subject and patch don't really fit together anymore. This is
> mostly cleanup (code movement) now, and I wonder whether
> this
Will adjust and resend.
Christoph
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
prev parent reply other threads:[~2012-10-26 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 13:54 [PATCH] MCE: support cpu notification chain Christoph Egger
2012-10-25 14:10 ` Jan Beulich
2012-10-25 14:18 ` Christoph Egger
2012-10-25 14:45 ` Christoph Egger
2012-10-25 14:57 ` Jan Beulich
2012-10-26 8:24 ` Christoph Egger [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=508A48B7.8050201@amd.com \
--to=christoph.egger@amd.com \
--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).