qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Babu Moger <babu.moger@amd.com>
To: pixo@polepetko.eu, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, babu.moger@amd.com
Subject: Re: [Qemu-devel] [PATCH] AMD Processor Topology Information
Date: Thu, 25 Jan 2018 16:56:39 -0500	[thread overview]
Message-ID: <20180125215639.73485-1-babu.moger@amd.com> (raw)
In-Reply-To: <20171103173037.17012-1-pixo@polepetko.eu>

Hi Stanislav,
I am working on to support hyperthreading feature on kvm/qemu guests for
AMD EPYC family of processors. I saw your patch series
https://patchwork.ozlabs.org/patch/834022/.
I am planning to refresh these patches with few changes. Let me know
if it is fine with you.
Thanks
Babu

  parent reply	other threads:[~2018-01-25 21:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 17:30 [Qemu-devel] [PATCH] AMD Processor Topology Information Stanislav Lanci
2017-11-08 12:44 ` Philippe Mathieu-Daudé
2017-11-09 16:04   ` pixo
2018-01-25 21:56 ` Babu Moger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-29 21:22 Stanislav Lanci
2017-10-29 22:14 ` no-reply

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=20180125215639.73485-1-babu.moger@amd.com \
    --to=babu.moger@amd.com \
    --cc=pixo@polepetko.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.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).