All of lore.kernel.org
 help / color / mirror / Atom feed
From: broonie@kernel.org
To: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>
Cc: Christian Borntraeger <borntraeger@linux.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Thomas Huth <thuth@redhat.com>
Subject: linux-next: manual merge of the kvm tree with the kvms390-fixes tree
Date: Tue,  2 Aug 2022 20:11:24 +0100	[thread overview]
Message-ID: <20220802191124.1985308-1-broonie@kernel.org> (raw)

Hi all,

Today's linux-next merge of the kvm tree got a conflict in:

  tools/testing/selftests/kvm/s390x/tprot.c

between commit:

  fd35ba6add67a ("KVM: s390: selftests: Use TAP interface in the tprot test")

from the kvms390-fixes tree and commit:

  0c073227df505 ("KVM: s390: selftests: Use TAP interface in the tprot test")

and subsequent commits from the kvm tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

diff --cc tools/testing/selftests/kvm/s390x/memop.c
index e704c6fa5758e,9113696d5178a..0000000000000
--- a/tools/testing/selftests/kvm/s390x/memop.c
+++ b/tools/testing/selftests/kvm/s390x/memop.c
diff --cc tools/testing/selftests/kvm/s390x/resets.c
index 889449a22e7ad,19486084eb309..0000000000000
--- a/tools/testing/selftests/kvm/s390x/resets.c
+++ b/tools/testing/selftests/kvm/s390x/resets.c
diff --cc tools/testing/selftests/kvm/s390x/tprot.c
index 14d74a9e7b3d4,a9a0b76e5fa45..0000000000000
--- a/tools/testing/selftests/kvm/s390x/tprot.c
+++ b/tools/testing/selftests/kvm/s390x/tprot.c
@@@ -183,30 -181,29 +181,35 @@@ static void guest_code(void
  	GUEST_SYNC(perform_next_stage(&i, mapped_0));
  }
  
- #define HOST_SYNC_NO_TAP(vmp, stage)						\
- ({										\
- 	struct kvm_vm *__vm = (vmp);						\
- 	struct ucall uc;							\
- 	int __stage = (stage);							\
- 										\
- 	vcpu_run(__vm, VCPU_ID);						\
- 	get_ucall(__vm, VCPU_ID, &uc);						\
- 	if (uc.cmd == UCALL_ABORT) {						\
- 		TEST_FAIL("line %lu: %s, hints: %lu, %lu", uc.args[1],		\
- 			  (const char *)uc.args[0], uc.args[2], uc.args[3]);	\
- 	}									\
- 	ASSERT_EQ(uc.cmd, UCALL_SYNC);						\
- 	ASSERT_EQ(uc.args[1], __stage);						\
+ #define HOST_SYNC_NO_TAP(vcpup, stage)				\
+ ({								\
+ 	struct kvm_vcpu *__vcpu = (vcpup);			\
+ 	struct ucall uc;					\
+ 	int __stage = (stage);					\
+ 								\
+ 	vcpu_run(__vcpu);					\
+ 	get_ucall(__vcpu, &uc);					\
+ 	if (uc.cmd == UCALL_ABORT)				\
+ 		REPORT_GUEST_ASSERT_2(uc, "hints: %lu, %lu");	\
+ 	ASSERT_EQ(uc.cmd, UCALL_SYNC);				\
+ 	ASSERT_EQ(uc.args[1], __stage);				\
+ })
+ 
+ #define HOST_SYNC(vcpu, stage)			\
+ ({						\
+ 	HOST_SYNC_NO_TAP(vcpu, stage);		\
+ 	ksft_test_result_pass("" #stage "\n");	\
  })
  
 +#define HOST_SYNC(vmp, stage)			\
 +({						\
 +	HOST_SYNC_NO_TAP(vmp, stage);		\
 +	ksft_test_result_pass("" #stage "\n");	\
 +})
 +
  int main(int argc, char *argv[])
  {
+ 	struct kvm_vcpu *vcpu;
  	struct kvm_vm *vm;
  	struct kvm_run *run;
  	vm_vaddr_t guest_0_page;

                 reply	other threads:[~2022-08-02 19:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220802191124.1985308-1-broonie@kernel.org \
    --to=broonie@kernel.org \
    --cc=borntraeger@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --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.