From: Luiz Capitulino <lcapitulino@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
rkrcmar@redhat.com, rostedt@goodmis.org, mhiramat@kernel.org,
mtosatti@redhat.com
Subject: Re: [PATCH v2 0/6] kvm: x86: export TSC information to user-space
Date: Fri, 16 Sep 2016 11:11:58 -0400 [thread overview]
Message-ID: <20160916111158.367cf470@redhat.com> (raw)
In-Reply-To: <888c2786-3dd5-d205-a433-b8d250702625@redhat.com>
On Fri, 16 Sep 2016 16:59:55 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 16/09/2016 16:59, Luiz Capitulino wrote:
> > On Fri, 16 Sep 2016 16:56:34 +0200
> > Paolo Bonzini <pbonzini@redhat.com> wrote:
> >
> >> On 16/09/2016 16:27, Luiz Capitulino wrote:
> >>> [Introduction will follow]
> >>>
> >>> Changelog
> >>> ---------
> >>>
> >>> v2
> >>>
> >>> - add tsc_offset field to struct kvm_vcpu_arch
> >>> - drop read_tsc_offset()
> >>> - add per-vcpu dir entries in debugfs
> >>> - export TSC scaling info (besides TSC offset)
> >>> - export the TSC offset as a signed number
> >>> - drop patch that wrongly tried to improve error
> >>> handling in kvm_create_vm_debugfs()
> >>
> >> I've tested this patch on an AMD machine with TSC scaling, so I'm
> >> pushing it shortly to kvm/queue.
> >
> > Thanks for the testing! Btw, I don't mind letting it sit on the
> > list for a few days for review (well, no submitter should mind
> > this).
>
> That's what kvm/queue is for. :)
Makes sense.
prev parent reply other threads:[~2016-09-16 15:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 14:27 [PATCH v2 0/6] kvm: x86: export TSC information to user-space Luiz Capitulino
2016-09-16 14:27 ` [PATCH 1/6] kvm: x86: add tsc_offset field to struct kvm_vcpu_arch Luiz Capitulino
2016-09-16 14:27 ` [PATCH 2/6] kvm: x86: drop read_tsc_offset() Luiz Capitulino
2016-09-19 15:30 ` Jim Mattson
2016-09-19 15:34 ` Paolo Bonzini
2016-09-19 22:18 ` Jim Mattson
2016-09-20 5:37 ` Paolo Bonzini
2016-09-21 15:19 ` Jim Mattson
2016-09-21 15:22 ` Paolo Bonzini
2016-09-21 15:31 ` Jim Mattson
2016-09-16 14:27 ` [PATCH 3/6] kvm: kvm_destroy_vm_debugfs(): check debugfs_stat_data pointer Luiz Capitulino
2016-09-16 14:27 ` [PATCH 4/6] kvm: add stubs for arch specific debugfs support Luiz Capitulino
2016-09-16 14:27 ` [PATCH 5/6] kvm: create per-vcpu dirs in debugfs Luiz Capitulino
2016-09-16 14:27 ` [PATCH 6/6] kvm: x86: export TSC information to user-space Luiz Capitulino
2016-09-16 14:56 ` [PATCH v2 0/6] " Paolo Bonzini
2016-09-16 14:59 ` Luiz Capitulino
2016-09-16 14:59 ` Paolo Bonzini
2016-09-16 15:11 ` Luiz Capitulino [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=20160916111158.367cf470@redhat.com \
--to=lcapitulino@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=rostedt@goodmis.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 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.