From: gengdongjiu <gengdongjiu@huawei.com>
To: Christoffer Dall <cdall@linaro.org>
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: Tue, 17 Oct 2017 22:00:59 +0800 [thread overview]
Message-ID: <0b35fe8c-59d9-96bd-2e61-66e7a2d463fc@huawei.com> (raw)
In-Reply-To: <20171016195901.GA5753@lvm>
Hi Christoffer
On 2017/10/17 3:59, Christoffer Dall wrote:
> 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 for your reminder, today I found a arm32 board and have tested it.
So I have tested in both arm32 and arm64. please review it. thanks.
> Thanks,
> -Christoffer
>
> .
>
next prev parent reply other threads:[~2017-10-17 14:00 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
2017-10-17 14:00 ` gengdongjiu [this message]
-- 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=0b35fe8c-59d9-96bd-2e61-66e7a2d463fc@huawei.com \
--to=gengdongjiu@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=cdall@linaro.org \
--cc=christoffer.dall@linaro.org \
--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