public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoffer Dall <cdall@linaro.org>
To: gengdongjiu <gengdongjiu@huawei.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
	"will.deacon@arm.com" <will.deacon@arm.com>,
	"christoffer.dall@linaro.org" <christoffer.dall@linaro.org>,
	"rkrcmar@redhat.com" <rkrcmar@redhat.com>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: KVM: set right LR register value for 32 bit guest when inject abort
Date: Mon, 16 Oct 2017 21:59:01 +0200	[thread overview]
Message-ID: <20171016195901.GA5753@lvm> (raw)
In-Reply-To: <0184EA26B2509940AA629AE1405DD7F201699F61@DGGEMA503-MBX.china.huawei.com>

On Mon, Oct 16, 2017 at 04:10:01PM +0000, gengdongjiu wrote:
> Hi Marc,
> 
> > 
> > Please also update the 32bit code accordingly, as it looks broken too.
> 
> I have updated the 32 bit code according, in my hand, there is no arm32 host environment,
> So there is no method to verify it in the arm32 host, only verify the patch in the arm64 host.
> 
> Anyway I firstly send the patch out for review. Thanks.
> 
In this case, if you just clearly specify in the patches you send out
that the 32-bit one is untested, you can ask someone to test it for you.

Thanks,
-Christoffer

  reply	other threads:[~2017-10-16 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 16:10 [PATCH] arm64: KVM: set right LR register value for 32 bit guest when inject abort gengdongjiu
2017-10-16 19:59 ` Christoffer Dall [this message]
2017-10-17 14:00   ` gengdongjiu
  -- strict thread matches above, loose matches on Subject: below --
2017-10-13 14:29 gengdongjiu
2017-10-13 15:12 ` Marc Zyngier
2017-10-15  3:11   ` gengdongjiu
2017-10-12 16:44 Dongjiu Geng
2017-10-13  9:28 ` Marc Zyngier

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=20171016195901.GA5753@lvm \
    --to=cdall@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=christoffer.dall@linaro.org \
    --cc=gengdongjiu@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=rkrcmar@redhat.com \
    --cc=will.deacon@arm.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