Kernel KVM-PPC virtualization development
 help / color / mirror / Atom feed
From: Laurentiu Tudor <b10716@freescale.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 1/2] KVM: PPC: e6500: Handle LRAT error exception
Date: Thu, 01 Oct 2015 09:12:30 +0000	[thread overview]
Message-ID: <560CF8FE.50603@freescale.com> (raw)
In-Reply-To: <5603F684.9020501@freescale.com>

On 09/30/2015 01:32 PM, Laurentiu Tudor wrote:
> On 09/25/2015 03:10 AM, Scott Wood wrote:
>> On Thu, 2015-09-24 at 16:11 +0300, Laurentiu Tudor wrote:

[snip]

>>> diff --git a/arch/powerpc/kvm/e500_mmu_host.c 
>>> b/arch/powerpc/kvm/e500_mmu_host.c
>>> index 12d5c67..99ad88a 100644
>>> --- a/arch/powerpc/kvm/e500_mmu_host.c
>>> +++ b/arch/powerpc/kvm/e500_mmu_host.c
>>> @@ -96,6 +96,112 @@ static inline void __write_host_tlbe(struct 
>>> kvm_book3e_206_tlb_entry *stlbe,
>>>                                     stlbe->mas2, stlbe->mas7_3);
>>>  }
>>>  
>>> +#if defined(CONFIG_64BIT) && defined(CONFIG_KVM_BOOKE_HV)
>>> +static int lrat_next(void)
>>> +{
>>
>> Will anything break by removing the CONFIG_64BIT condition, even if we don't 
>> have a 32-bit target that uses this?
> 
> Not completly certain but i remember getting compile or link errors
> on 32-bit e500mc or e500v2. I can recheck if you want.
>

I double-checked this and indeed it doesn't compile on 32-bit because
lrat_next() calls get_paca().

---
Best Regards, Laurentiu


      parent reply	other threads:[~2015-10-01  9:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 13:11 [PATCH 1/2] KVM: PPC: e6500: Handle LRAT error exception Laurentiu Tudor
2015-09-25  0:10 ` Scott Wood
2015-09-30 10:32 ` Laurentiu Tudor
2015-09-30 11:27 ` Laurentiu Tudor
2015-09-30 16:55 ` Scott Wood
2015-10-01  9:12 ` Laurentiu Tudor [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=560CF8FE.50603@freescale.com \
    --to=b10716@freescale.com \
    --cc=kvm-ppc@vger.kernel.org \
    /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