[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130523170927.GM26157@redhat.com>
Date: Thu, 23 May 2013 20:09:27 +0300
From: Gleb Natapov <gleb@...hat.com>
To: David Daney <ddaney@...iumnetworks.com>
Cc: David Daney <ddaney.cavm@...il.com>, linux-mips@...ux-mips.org,
ralf@...ux-mips.org, kvm@...r.kernel.org,
Sanjay Lal <sanjayl@...asys.com>, linux-kernel@...r.kernel.org,
David Daney <david.daney@...ium.com>
Subject: Re: [PATCH v5 0/6] mips/kvm: Fix ABI for compatibility with 64-bit
guests.
On Thu, May 23, 2013 at 09:58:00AM -0700, David Daney wrote:
> On 05/23/2013 03:28 AM, Gleb Natapov wrote:
> >On Wed, May 22, 2013 at 11:43:50AM -0700, David Daney wrote:
> >>From: David Daney <david.daney@...ium.com>
> >>
> >Please regenerate against master. arch/mips/include/asm/kvm.h does not
> >exists any more.
>
> New patch sent. I gather from this message, that you want to merge
> this particular set via your tree instead of Ralf's MIPS tree.
> That's fine with me. However, we were hoping to have these ABI
> fixing patches pushed to Linus before 3.10 releases, so that there
> don't exist kernel versions with the defective ABI.
>
I do plan to push them to 3.10 that is why I asked to generate them
against master ("next" branch is for next merge window)
> Future patch sets may affect core MIPS architecture files, and
> therefore may not be so amenable to merging via the KVM tree. We
> will have to figure out how to handle that.
>
Are you talking about initial MIPS HW vitalization support? Lets see
the patch series. If core changes are to big for for Ralf to ack them
and push through kvm.git then we can push them via MPIS tree.
--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists