Hi Paolo, On Thu, Sep 08, 2016 at 03:34:59PM +0200, Paolo Bonzini wrote: > > > On 08/09/2016 14:13, James Hogan wrote: > > These patches fix a couple of problems when using MIPS KVM on a host > > kernel with Enhanced Virtual Addressing (EVA) enabled. > > > > Patch 1 fixes the HVA error codes like s390 does, due to PAGE_OFFSET > > potentially being as low as 0. > > > > Patch 2 allows MMIO to be emulated from TLB refill exceptions as well as > > address error exceptions (since EVA configurations may make KSeg1 > > addresses TLB mapped to user mode). > > > > It isn't complete as there are still a couple of cases where KVM tries > > to directly access guest memory using normal loads and stores (which > > doesn't work with EVA's overlapping usermode & kernel mode address > > spaces). That really needs fixing properly anyway to handle the > > potential for TLB invalidations (and the resulting refills & page > > faults). > > > > For KVM to work on EVA hosts also requires some MIPS architecture > > changes, as found in my recent "MIPS: General EVA fixes & cleanups" > > patchset. > > Since there aren't any overlaps with 4.8 patches, feel free to send a > pull request for these and any other patches you might have in the rest > of this cycle. Yeh, I'd like to start working with pull requests (and topic branches where applicable) from now on. I'd normally still post patches to the lists even if I immediately apply them (I should perhaps move you from To to Cc), is that okay? Any particular times in the cycle you want pull requests, or deadlines for new features for the next release? Should I get a branch added to linux-next, or just rely on kvm/next after stuff is pulled? Any other preferences? Thanks James
Attachment:
signature.asc
Description: Digital signature
