From: Joerg Roedel <joro@8bytes.org>
To: Mark Langsdorf <mark.langsdorf@amd.com>
Cc: linux-kernel@vger.kernel.org, avi@qumranet.com, avi@redhat.com,
kvm@vger.kernel.org
Subject: Re: [PATCH][retry 2] Support Pause Filter in AMD processors
Date: Sat, 3 Oct 2009 00:37:22 +0200 [thread overview]
Message-ID: <20091002223722.GC23379@8bytes.org> (raw)
In-Reply-To: <200910021449.59284.mark.langsdorf@amd.com>
On Fri, Oct 02, 2009 at 02:49:59PM -0500, Mark Langsdorf wrote:
> +static int pause_interception(struct vcpu_svm *svm)
> +{
> + static int pause_count = 0;
> +
> + kvm_vcpu_on_spin(&(svm->vcpu));
> +printk(KERN_ERR "MJLL pause intercepted %d\n", ++pause_count);
Debugging leftover?
> + return 1;
> +}
next prev parent reply other threads:[~2009-10-02 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 19:49 [PATCH][retry 2] Support Pause Filter in AMD processors Mark Langsdorf
2009-10-02 22:37 ` Joerg Roedel [this message]
2009-10-06 19:25 ` [PATCH][retry 3] " Mark Langsdorf
2009-10-12 19:17 ` Marcelo Tosatti
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=20091002223722.GC23379@8bytes.org \
--to=joro@8bytes.org \
--cc=avi@qumranet.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.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 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).