All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	kvm@vger.kernel.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
	"Shuah Khan" <shuah@kernel.org>,
	"David Hildenbrand" <david@redhat.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"Andrew Jones" <drjones@redhat.com>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-s390@vger.kernel.org
Subject: Re: [RFC PATCH 4/4] KVM: selftests: Add the sync_regs test for s390x
Date: Mon, 20 May 2019 13:19:40 +0200	[thread overview]
Message-ID: <3e462f1d-c9c0-ac26-ed59-182fbbf60340@redhat.com> (raw)
In-Reply-To: <20190516111253.4494-5-thuth@redhat.com>

On 16/05/19 13:12, Thomas Huth wrote:
> +#define VCPU_ID 5
> +
> +static void guest_code(void)
> +{
> +	for (;;) {
> +		asm volatile ("diag 0,0,0x501");
> +		asm volatile ("ahi 11,1");
> +	}

I'd like this to use something like

	register u32 stage = 0 asm("11");
	...
	stage++

instead (yes, it should be fixed in x86 too).

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: pbonzini at redhat.com (Paolo Bonzini)
Subject: [RFC PATCH 4/4] KVM: selftests: Add the sync_regs test for s390x
Date: Mon, 20 May 2019 13:19:40 +0200	[thread overview]
Message-ID: <3e462f1d-c9c0-ac26-ed59-182fbbf60340@redhat.com> (raw)
In-Reply-To: <20190516111253.4494-5-thuth@redhat.com>

On 16/05/19 13:12, Thomas Huth wrote:
> +#define VCPU_ID 5
> +
> +static void guest_code(void)
> +{
> +	for (;;) {
> +		asm volatile ("diag 0,0,0x501");
> +		asm volatile ("ahi 11,1");
> +	}

I'd like this to use something like

	register u32 stage = 0 asm("11");
	...
	stage++

instead (yes, it should be fixed in x86 too).

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: pbonzini@redhat.com (Paolo Bonzini)
Subject: [RFC PATCH 4/4] KVM: selftests: Add the sync_regs test for s390x
Date: Mon, 20 May 2019 13:19:40 +0200	[thread overview]
Message-ID: <3e462f1d-c9c0-ac26-ed59-182fbbf60340@redhat.com> (raw)
Message-ID: <20190520111940.QS6uujBov-7ZkNiixVau8i913e6acQZy1Mz-AM_RO9U@z> (raw)
In-Reply-To: <20190516111253.4494-5-thuth@redhat.com>

On 16/05/19 13:12, Thomas Huth wrote:
> +#define VCPU_ID 5
> +
> +static void guest_code(void)
> +{
> +	for (;;) {
> +		asm volatile ("diag 0,0,0x501");
> +		asm volatile ("ahi 11,1");
> +	}

I'd like this to use something like

	register u32 stage = 0 asm("11");
	...
	stage++

instead (yes, it should be fixed in x86 too).

Paolo

  reply	other threads:[~2019-05-20 11:19 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 11:12 [RFC PATCH 0/4] KVM selftests for s390x Thomas Huth
2019-05-16 11:12 ` Thomas Huth
2019-05-16 11:12 ` thuth
2019-05-16 11:12 ` [RFC PATCH 1/4] KVM: selftests: Guard struct kvm_vcpu_events with __KVM_HAVE_VCPU_EVENTS Thomas Huth
2019-05-16 11:12   ` Thomas Huth
2019-05-16 11:12   ` thuth
2019-05-16 11:22   ` David Hildenbrand
2019-05-16 11:22     ` David Hildenbrand
2019-05-16 11:22     ` david
2019-05-20  7:12   ` Christian Borntraeger
2019-05-20  7:12     ` Christian Borntraeger
2019-05-20  7:12     ` borntraeger
2019-05-20  8:08     ` Thomas Huth
2019-05-20  8:08       ` Thomas Huth
2019-05-20  8:08       ` thuth
2019-05-20  8:13       ` Christian Borntraeger
2019-05-20  8:13         ` Christian Borntraeger
2019-05-20  8:13         ` borntraeger
2019-05-16 11:12 ` [RFC PATCH 2/4] KVM: selftests: Align memory region addresses to 1M on s390x Thomas Huth
2019-05-16 11:12   ` Thomas Huth
2019-05-16 11:12   ` thuth
2019-05-16 11:30   ` David Hildenbrand
2019-05-16 11:30     ` David Hildenbrand
2019-05-16 11:30     ` david
2019-05-16 11:59     ` Thomas Huth
2019-05-16 11:59       ` Thomas Huth
2019-05-16 11:59       ` thuth
2019-05-16 12:08       ` David Hildenbrand
2019-05-16 12:08         ` David Hildenbrand
2019-05-16 12:08         ` david
2019-05-16 11:12 ` [RFC PATCH 3/4] KVM: selftests: Add processor code for s390x Thomas Huth
2019-05-16 11:12   ` Thomas Huth
2019-05-16 11:12   ` thuth
2019-05-16 11:12 ` [RFC PATCH 4/4] KVM: selftests: Add the sync_regs test " Thomas Huth
2019-05-16 11:12   ` Thomas Huth
2019-05-16 11:12   ` thuth
2019-05-20 11:19   ` Paolo Bonzini [this message]
2019-05-20 11:19     ` Paolo Bonzini
2019-05-20 11:19     ` pbonzini
2019-05-23 10:56   ` Andrew Jones
2019-05-23 10:56     ` Andrew Jones
2019-05-23 10:56     ` drjones
2019-05-23 11:19     ` Thomas Huth
2019-05-23 11:19       ` Thomas Huth
2019-05-23 11:19       ` thuth
2019-05-20 11:20 ` [RFC PATCH 0/4] KVM selftests " Paolo Bonzini
2019-05-20 11:20   ` Paolo Bonzini
2019-05-20 11:20   ` pbonzini
2019-05-20 11:30   ` Thomas Huth
2019-05-20 11:30     ` Thomas Huth
2019-05-20 11:30     ` thuth
2019-05-20 11:43     ` Paolo Bonzini
2019-05-20 11:43       ` Paolo Bonzini
2019-05-20 11:43       ` pbonzini
2019-05-20 11:43       ` Paolo Bonzini
2019-05-22  8:44       ` Andrew Jones
2019-05-22  8:44         ` Andrew Jones
2019-05-22  8:44         ` drjones

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=3e462f1d-c9c0-ac26-ed59-182fbbf60340@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=drjones@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=rkrcmar@redhat.com \
    --cc=shuah@kernel.org \
    --cc=thuth@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.