qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Harivel <aharivel@redhat.com>
To: pbonzini@redhat.com
Cc: qemu-devel@nongnu.org, Anthony Harivel <aharivel@redhat.com>
Subject: [PATCH 0/2] Fix RAPL MSR support in staging
Date: Fri, 26 Jul 2024 12:26:30 +0200	[thread overview]
Message-ID: <20240726102632.1324432-1-aharivel@redhat.com> (raw)

Hi Paolo,

RAPL MSR has landed in staging with few scratches.

Here a couple of patches to solves CID 1558553 and 1558557.

Anthony

Anthony Harivel (2):
  target/i386: Fix typo that assign same value twice
  target/i386: Clean output of vmsr_read_thread_stat()

 target/i386/kvm/kvm.c         | 4 ++--
 target/i386/kvm/vmsr_energy.c | 5 +++--
 2 files changed, 5 insertions(+), 4 deletions(-)

-- 
2.45.2



             reply	other threads:[~2024-07-26 10:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26 10:26 Anthony Harivel [this message]
2024-07-26 10:26 ` [PATCH 1/2] target/i386: Fix typo that assign same value twice Anthony Harivel
2024-07-26 10:26 ` [PATCH 2/2] target/i386: Clean output of vmsr_read_thread_stat() Anthony Harivel

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=20240726102632.1324432-1-aharivel@redhat.com \
    --to=aharivel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@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).