xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Egger <chegger@amazon.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] tools/xen-mceinj: support AMD
Date: Thu, 30 May 2013 16:29:25 +0200	[thread overview]
Message-ID: <51A76245.3060606@amazon.de> (raw)
In-Reply-To: <51544435.1050700@amazon.de>

On 28.03.13 14:23, Christoph Egger wrote:
> On 28.03.13 12:44, Jan Beulich wrote:
>>>>> On 27.03.13 at 14:41, Egger Christoph <chegger@amazon.de> wrote:
>>
>> Didn't you also require a hypervisor side change for
>>
>>> +#define MC4_type_MISC1      0x4
>>> +#define MC4_type_MISC2      0x5
>>> +#define MC4_type_MISC3      0x6
>>
>> which also gets me back to the previously asked question why
>> this is done only for bank 4.
> 
> These MSRs only exist on bank 4.
> 
>>> -    sprintf(path, "/local/domain/%d/memory/target", domid);
>>> +    snprintf(path, sizeof(path), "/local/domain/%d/memory/target",
>>> domid);
>>
>> This continues to be valid, but unrelated.
>>
>>> -    int type = MCE_SRAO_MEM;
>>> +    int type;
>>> ...
>>> +    if (cpu_vendor == CPU_VENDOR_AMD)
>>> +        type = AMD_MCE_MEM;
>>> +    if (cpu_vendor == CPU_VENDOR_INTEL)
>>> +        type = INTEL_MCE_SRAO_MEM;
>>
>> still leaves type uninitialized for the non-Intel, non-AMD case. And
>> some compilers aren't going to be able to figure out that the
>> variable only gets used for either of these two cases, and will raise
>> a warning.
> 
> I haven't seen any warning but ok, will fix.

I am sending a new with this fixed.

Christoph

  parent reply	other threads:[~2013-05-30 14:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 13:41 [PATCH] tools/xen-mceinj: support AMD Egger Christoph
2013-03-28 11:44 ` Jan Beulich
2013-03-28 13:23   ` Christoph Egger
2013-03-28 13:58     ` Jan Beulich
2013-03-28 14:11       ` Christoph Egger
2013-04-11  7:53         ` Christoph Egger
2013-05-30 14:29     ` Christoph Egger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-10-05 14:07 Christoph Egger
2012-10-19 13:10 ` Christoph Egger
2012-10-19 14:58   ` Jan Beulich
2012-10-19 15:01     ` Ian Jackson
2012-10-19 15:05       ` Jan Beulich
2012-11-12 16:25         ` Ian Campbell
2012-11-13  1:40           ` Hao, Xudong
2012-11-13  8:40             ` Jan Beulich
2012-10-29 10:20 ` Jan Beulich

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=51A76245.3060606@amazon.de \
    --to=chegger@amazon.de \
    --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).