public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel•org>
To: Murphy Zhou <jencce.kernel@gmail•com>
Cc: Gavin Shan <gshan@redhat•com>,
	linux-arm-kernel@lists•infradead.org, kvm@vger•kernel.org,
	linux-next@vger•kernel.org
Subject: Re: linux-next arm64 kvm build error
Date: Fri, 06 Nov 2020 10:25:34 +0000	[thread overview]
Message-ID: <c1bd128a817a8c2677b9e68ee9215a31@kernel.org> (raw)
In-Reply-To: <20201106100929.pllgrxcdj3xjx47a@xzhoux.usersys.redhat.com>

On 2020-11-06 10:09, Murphy Zhou wrote:
> Hi,
> 
> It's introduced by this commit:
>     KVM: arm64: Use fallback mapping sizes for contiguous huge page 
> sizes
> and blocking further test.

It's already been reported, with a patch [1], and you can still test
with a 48bit VA configuration.

Thanks,

         M.

[1] https://lore.kernel.org/r/20201103003009.32955-1-gshan@redhat.com
-- 
Jazz is not dead. It just smells funny...

      reply	other threads:[~2020-11-06 10:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 10:09 linux-next arm64 kvm build error Murphy Zhou
2020-11-06 10:25 ` Marc Zyngier [this message]

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=c1bd128a817a8c2677b9e68ee9215a31@kernel.org \
    --to=maz@kernel$(echo .)org \
    --cc=gshan@redhat$(echo .)com \
    --cc=jencce.kernel@gmail$(echo .)com \
    --cc=kvm@vger$(echo .)kernel.org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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