3.16.7-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: James Hogan
commit ca5d25642e212f73492d332d95dc90ef46a0e8dc upstream.
Export the _save_msa asm function used by the lose_fpu(1) macro to GPL
modules so that KVM can make use of it whe
3.16.7-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: James Hogan
commit 3ce465e04bfd8de9956d515d6e9587faac3375dc upstream.
Export the _save_fp asm function used by the lose_fpu(1) macro to GPL
modules so that KVM can make use of it when
3.16.7-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: James Hogan
commit f798217dfd038af981a18bbe4bc57027a08bb182 upstream.
The FPU and DSP are enabled via the CP0 Status CU1 and MX bits by
kvm_mips_set_c0_status() on a guest exit, presu
Hi Andrea,
On 5 March 2015 at 18:17, Andrea Arcangeli wrote:
> Once an userfaultfd has been created and certain region of the process
> virtual address space have been registered into it, the thread
> responsible for doing the memory externalization can manage the page
> faults in userland by tal
On Mon, 2 Mar 2015 21:44:10 +0100
"Michael S. Tsirkin" wrote:
> > > Normally, hotunplug requires guest cooperation.
> > > IOW unplug request should send guest interrupt,
> > > then block until guest confirms it's not using the
> > > device anymore.
> > > virtio pci already handles that fine, can
On Wed, 4 Mar 2015 11:25:56 +0100
"Michael S. Tsirkin" wrote:
> On Wed, Mar 04, 2015 at 04:44:54PM +1030, Rusty Russell wrote:
> > "Michael S. Tsirkin" writes:
> > > On Mon, Mar 02, 2015 at 10:37:26AM +1030, Rusty Russell wrote:
> > >> Thomas Huth writes:
> > >> > On Thu, 26 Feb 2015 11:50:42 +
From: Michael Mueller
Most facility related decisions in KVM have to take into account:
- the facilities offered by the underlying run container (LPAR/VM)
- the facilities supported by the KVM code itself
- the facilities requested by a guest VM
This patch adds the KVM driver requested faciliti
From: Tony Krowiak
z/VM and LPAR enable key wrapping by default, lets do the same on KVM.
Signed-off-by: Tony Krowiak
Signed-off-by: Christian Borntraeger
---
arch/s390/kvm/kvm-s390.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/s390/kvm/kvm-s390.c b/arc
From: Michael Mueller
The function kvm_s390_vcpu_setup_model() now performs all cpu model realated
setup tasks for a vcpu. Besides cpuid and ibc initialization, facility list
assignment takes place during the setup step as well. The model setup has been
pulled to the begin of vcpu setup to allow
From: David Hildenbrand
If the I/O interrupt could not be written to the guest provided
area (e.g. access exception), a program exception was injected into the
guest but "inti" wasn't freed, therefore resulting in a memory leak.
In addition, the I/O interrupt wasn't reinjected. Therefore the deq
Under z/VM PQAP might trigger an operation exception if no crypto cards
are defined via APVIRTUAL or APDEDICATED.
[ 386.098666] Kernel BUG at 00135c56 [verbose debug info unavailable]
[ 386.098693] illegal operation: 0001 ilc:2 [#1] SMP
[...]
[ 386.098751] Krnl PSW : 0704c0018000 00
From: Eric Farman
Define and allocate space for both the host and guest views of
the vector registers for a given vcpu. The 32 vector registers
occupy 128 bits each (512 bytes total), but architecturally are
paired with 512 additional bytes of reserved space for future
expansion.
The kvm_sync_r
From: Thomas Huth
The common s390 function insn_length() results in slightly smaller
(and thus hopefully faster) code than the calculation of the
instruction length via a lookup-table. So let's use that function
in the interrupt delivery code, too.
Signed-off-by: Thomas Huth
Reviewed-by: Jens F
From: David Hildenbrand
trace-cmd fails to parse the instruction interception trace point:
"Error: expected type 5 but read 4
failed to read event print fmt for kvm_s390_intercept_instruction"
The result is an unformatted string in the output, with a warning:
"kvm_s390_intercept_instructio
-rc1 (2015-02-22 18:21:14 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git
tags/kvm-s390-next-20150306
for you to fetch changes up to 13211ea7b47db3d8ee2ff258a9a973a6d3aa3d43:
KVM: s390: Enable vector support for capable guest
From: Eric Farman
We finally have all the pieces in place, so let's include the
vector facility bit in the mask of available hardware facilities
for the guest to recognize. Also, enable the vector functionality
in the guest control blocks, to avoid a possible vector data
exception that would oth
From: Yannick Guerrini
Change 'architecuture' to 'architecture'
Signed-off-by: Yannick Guerrini
Message-Id: <1424989004-14412-1-git-send-email-yguerr...@tomshardware.fr>
Signed-off-by: Christian Borntraeger
---
arch/s390/kvm/gaccess.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
From: Eric Farman
The new SIGP order Store Additional Status at Address is totally
handled by user space, but we should still record the occurrence
of this order in the kernel code.
Signed-off-by: Eric Farman
Reviewed-by: Thomas Huth
Reviewed-by: David Hildenbrand
Signed-off-by: Christian Bor
From: Thomas Huth
When certain program exceptions (e.g. DAT access exceptions) occur,
the current instruction has to be nullified, i.e. the old PSW that
gets written into the low-core has to point to the beginning of the
instruction again, and not to the beginning of the next instruction.
Thus we
From: Thomas Huth
When the SIE exited by a DAT access exceptions which we can not
resolve, the guest tried to access a page which is out of bounds
and can not be paged-in. In this case we have to signal the bad
access by injecting an address exception. However, address exceptions
are either suppr
From: Eric Farman
Store additional status in the machine check handler, in order to
collect status (such as vector registers) that is not defined by
store status.
Signed-off-by: Eric Farman
Reviewed-by: Thomas Huth
Reviewed-by: David Hildenbrand
Reviewed-by: Cornelia Huck
Signed-off-by: Chri
From: Michael Mueller
The facility lists were not fully copied.
Signed-off-by: Michael Mueller
Signed-off-by: Christian Borntraeger
---
arch/s390/kvm/kvm-s390.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
index 18
From: David Hildenbrand
The reinjection of an I/O interrupt can fail if the list is at the limit
and between the dequeue and the reinjection, another I/O interrupt is
injected (e.g. if user space floods kvm with I/O interrupts).
This patch avoids this memory leak and returns -EFAULT in this spec
From: Alexander Yarygin
The guest debug functions work on absolute addresses and should use the
read_guest_abs() function rather than general read_guest() that
works with logical addresses.
Cc: David Hildenbrand
Signed-off-by: Alexander Yarygin
Reviewed-by: David Hildenbrand
Reviewed-by: Thom
From: Michael Mueller
With patch "include guest facilities in kvm facility test" it is no
longer necessary to have special handling for the non-LPAR case.
Signed-off-by: Michael Mueller
Signed-off-by: Christian Borntraeger
---
arch/s390/kvm/kvm-s390.c | 17 +
1 file changed, 1
From: Ekaterina Tumanova
s390 documentation requires words 0 and 10-15 to be reserved and stored as
zeros. As we fill out all other fields, we can memset the full structure.
Signed-off-by: Ekaterina Tumanova
Cc: sta...@vger.kernel.org
Reviewed-by: David Hildenbrand
Signed-off-by: Christian Bor
From: Eric Farman
A new exception type for vector instructions is introduced with
the new processor, but is handled exactly like a Data Exception
which is already handled by the system.
Signed-off-by: Eric Farman
Reviewed-by: David Hildenbrand
Acked-by: Christian Borntraeger
Signed-off-by: Ch
* Marcelo Tosatti | 2015-01-14 15:12:52 [-0200]:
Against which tree was this prepared? Could please rebase it against
v3.18.7-rt2? Because a I see "fuzz 2", the mips file is gone and
s390 rejects almost every chunk.
And there was that mips chunk Steven noticed.
Patch #2 seems to apply but since it
On 03/05/2015 10:17 AM, Andrea Arcangeli wrote:
> Add documentation.
>
> Signed-off-by: Andrea Arcangeli
> ---
> Documentation/vm/userfaultfd.txt | 97
>
> 1 file changed, 97 insertions(+)
> create mode 100644 Documentation/vm/userfaultfd.txt
Just a gr
On Thu, Mar 05, 2015 at 10:30:34PM -0800, Greg Kroah-Hartman wrote:
> On Thu, Mar 05, 2015 at 04:08:44PM +, James Hogan wrote:
> > [ Upstream commit 3ce465e04bfd8de9956d515d6e9587faac3375dc ]
> >
> > Export the _save_fp asm function used by the lose_fpu(1) macro to GPL
> > modules so that KVM
Andrey Korolyov writes:
> On Fri, Mar 6, 2015 at 1:14 AM, Andrey Korolyov wrote:
>> Hello,
>>
>> recently I`ve got a couple of shiny new Intel 2620v2s for future
>> replacement of the E5-2620v1, but I experienced relatively many events
>> with emulation errors, all traces looks simular to the on
Hi,
I have read a good documentation
(http://fds-team.de/cms/articles/2013-12/use-a-real-windows-7-partition-in-virtualbox-kvm-vmware-player-u.html)
explaining how to use a physical disk/partition and clone it to KVM image.
I am wondering if someone has some how-to with an UEFI partition?
My obj
On Fri, Mar 6, 2015 at 12:13 PM, Ben wrote:
> Hi,
>
> I have read a good documentation
> (http://fds-team.de/cms/articles/2013-12/use-a-real-windows-7-partition-in-virtualbox-kvm-vmware-player-u.html)
> explaining how to use a physical disk/partition and clone it to KVM image.
> I am wondering if
On Fri, Mar 06, 2015 at 08:22:49AM -0800, Guenter Roeck wrote:
> On Thu, Mar 05, 2015 at 10:30:34PM -0800, Greg Kroah-Hartman wrote:
> > On Thu, Mar 05, 2015 at 04:08:44PM +, James Hogan wrote:
> > > [ Upstream commit 3ce465e04bfd8de9956d515d6e9587faac3375dc ]
> > >
> > > Export the _save_fp a
On 06/03/2015 18:29, Mauricio Tavares wrote:
>> > My objective is to clone a partition of Windows 7 from a physical disk.
>> > (not the entire disk as it is a 256GB disk and my disk on my host is as
>> > well a 256GB so I would not get a byte of free space doing that! only
>> > need to clone the
On 03/04/2015 03:35 AM, Catalin Marinas wrote:
> (please try to avoid top-posting)
>
> On Mon, Mar 02, 2015 at 06:20:19PM -0800, Mario Smarduch wrote:
>> On 03/02/2015 08:31 AM, Christoffer Dall wrote:
>>> However, my concern with these patches are on two points:
>>>
>>> 1. It's not a fix-all. We
From: David Kaplan
Another patch in my war on emulate_on_interception() use as a svm exit handler.
These were pulled out of a larger patch at the suggestion of Radim Krcmar, see
https://lkml.org/lkml/2015/2/25/559
Signed-off-by: David Kaplan
[separated out just cr_interception part from larger
On Fri, Mar 06, 2015 at 09:45:16AM -0800, Greg Kroah-Hartman wrote:
> On Fri, Mar 06, 2015 at 08:22:49AM -0800, Guenter Roeck wrote:
> > On Thu, Mar 05, 2015 at 10:30:34PM -0800, Greg Kroah-Hartman wrote:
> > > On Thu, Mar 05, 2015 at 04:08:44PM +, James Hogan wrote:
> > > > [ Upstream commit 3
From: David Kaplan
Another patch in my war on emulate_on_interception() use as a svm exit handler.
These were pulled out of a larger patch at the suggestion of Radim Krcmar, see
https://lkml.org/lkml/2015/2/25/559
Changes since v1:
* fixed typo introduced after test, retested
Signed-of
On 03/05/2015 09:43 AM, Paolo Bonzini wrote:
>
>
> On 05/03/2015 15:58, Catalin Marinas wrote:
>>> It would especially suck if the user has a cluster with different
>>> machines, some of them coherent and others non-coherent, and then has to
>>> debug why the same configuration works on some mach
On Wed, Mar 04, 2015 at 01:02:43PM -0700, Alex Williamson wrote:
> This copies the same support from pci-stub for exactly the same
> purpose, enabling a set of PCI IDs to be automatically added to the
> driver's dynamic ID table at module load time. The code here is
> pretty simple and both vfio-p
On Fri, Mar 6, 2015 at 7:57 PM, Bandan Das wrote:
> Andrey Korolyov writes:
>
>> On Fri, Mar 6, 2015 at 1:14 AM, Andrey Korolyov wrote:
>>> Hello,
>>>
>>> recently I`ve got a couple of shiny new Intel 2620v2s for future
>>> replacement of the E5-2620v1, but I experienced relatively many events
>
Alex:
Thanks for your quick reply and the information. One question though:
When you say contact the platform vendor, are you talking about the
vendor of the GPU card (NVidia) or the vendor of the system hardware
(HP)? I.E. is the problem in the system BIOS/firmware or in the firmware
of the G
On Fri, 2015-03-06 at 22:10 -0500, Steven DuChene wrote:
> Alex:
> Thanks for your quick reply and the information. One question though:
> When you say contact the platform vendor, are you talking about the
> vendor of the GPU card (NVidia) or the vendor of the system hardware
> (HP)? I.E. is th
44 matches
Mail list logo
