All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: Wei Huang <wei@redhat.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, rkrcmar@redhat.com
Subject: Re: [kvm-unit-tests RFC 2/3] x86/pmu: Rename pmu.c code to intel_pmu.c
Date: Fri, 4 Aug 2017 10:00:30 +0200	[thread overview]
Message-ID: <20170804080030.yeeasw5ypk4uamif@kamzik.brq.redhat.com> (raw)
In-Reply-To: <1501820670-23194-3-git-send-email-wei@redhat.com>

On Thu, Aug 03, 2017 at 11:24:29PM -0500, Wei Huang wrote:
> Many code in pmu.c is Intel-specific (e.g. fixed counters, global
> ctrl). This patch renames pmu.c to intel_pmu.c. The makefile and
> unit-test config file are also changed acccordingly.
> 
> Signed-off-by: Wei Huang <wei@redhat.com>
> ---
>  x86/Makefile.common |   2 +-
>  x86/intel_pmu.c     | 379 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>  x86/pmu.c           | 379 ----------------------------------------------------
>  x86/unittests.cfg   |   4 +-
>  4 files changed, 382 insertions(+), 382 deletions(-)
>  create mode 100644 x86/intel_pmu.c
>  delete mode 100644 x86/pmu.c

It'd be best to create this patch with 'format-patch -M'

Thanks,
drew

  reply	other threads:[~2017-08-04  8:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04  4:24 [kvm-unit-tests RFC 0/3] x86/pmu: Add AMD vPMU testing code Wei Huang
2017-08-04  4:24 ` [kvm-unit-tests RFC 1/3] x86/pmu: Move common x86 PMU definitions to pmu.h Wei Huang
2017-08-04  7:59   ` Andrew Jones
2017-08-04  4:24 ` [kvm-unit-tests RFC 2/3] x86/pmu: Rename pmu.c code to intel_pmu.c Wei Huang
2017-08-04  8:00   ` Andrew Jones [this message]
2017-08-04 15:44     ` Wei Huang
2017-08-04  4:24 ` [kvm-unit-tests RFC 3/3] x86/pmu: Create AMD PMU test code Wei Huang
2017-08-04  8:14   ` Andrew Jones
2017-08-04 15:49     ` Wei Huang

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=20170804080030.yeeasw5ypk4uamif@kamzik.brq.redhat.com \
    --to=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=wei@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.