similar to: [PATCH] tools/virtio: Fix build

On 13.10.19 13:52, Michael S. Tsirkin wrote: > On Sun, Oct 13, 2019 at 11:03:30AM +0200, Jan Kiszka wrote: >> From: Jan Kiszka <jan.kiszka at siemens.com> >> >> Various changes in the recent kernel versions broke the build due to >> missing function and header stubs. >> >> Signed-off-by: Jan Kiszka <jan.kiszka at siemens.com> > > Thanks!

On 13.10.19 13:52, Michael S. Tsirkin wrote: > On Sun, Oct 13, 2019 at 11:03:30AM +0200, Jan Kiszka wrote: >> From: Jan Kiszka <jan.kiszka at siemens.com> >> >> Various changes in the recent kernel versions broke the build due to >> missing function and header stubs. >> >> Signed-off-by: Jan Kiszka <jan.kiszka at siemens.com> > > Thanks!

On Sun, Oct 13, 2019 at 02:01:03PM +0200, Jan Kiszka wrote: > On 13.10.19 13:52, Michael S. Tsirkin wrote: > > On Sun, Oct 13, 2019 at 11:03:30AM +0200, Jan Kiszka wrote: > >> From: Jan Kiszka <jan.kiszka at siemens.com> > >> > >> Various changes in the recent kernel versions broke the build due to > >> missing function and header stubs. >

On Sun, Oct 13, 2019 at 11:03:30AM +0200, Jan Kiszka wrote: > From: Jan Kiszka <jan.kiszka at siemens.com> > > Various changes in the recent kernel versions broke the build due to > missing function and header stubs. > > Signed-off-by: Jan Kiszka <jan.kiszka at siemens.com> Thanks! I think it's already fixes in the vhost tree. That tree also includes a bugfix

On 13.10.19 14:20, Michael S. Tsirkin wrote: > On Sun, Oct 13, 2019 at 02:01:03PM +0200, Jan Kiszka wrote: >> On 13.10.19 13:52, Michael S. Tsirkin wrote: >>> On Sun, Oct 13, 2019 at 11:03:30AM +0200, Jan Kiszka wrote: >>>> From: Jan Kiszka <jan.kiszka at siemens.com> >>>> >>>> Various changes in the recent kernel versions broke the build

On Mon, Jan 22, 2018 at 8:12 AM, Jan Kiszka <jan.kiszka at siemens.com> wrote: > From: Jan Kiszka <jan.kiszka at siemens.com> > > Not sure if those two worked by design or just by chance so far. In any > case, it's at least cleaner and clearer to express this in a single > config statement. Congrats! You found by the way a bug in commit

On Mon, Jan 22, 2018 at 8:12 AM, Jan Kiszka <jan.kiszka at siemens.com> wrote: > From: Jan Kiszka <jan.kiszka at siemens.com> > > Not sure if those two worked by design or just by chance so far. In any > case, it's at least cleaner and clearer to express this in a single > config statement. Congrats! You found by the way a bug in commit

On Mon, Jan 22, 2018 at 8:12 AM, Jan Kiszka <jan.kiszka at siemens.com> wrote: > #include <linux/export.h> > #include <linux/pci.h> > #include <asm/pci_x86.h> > +#include <asm/jailhouse_para.h> Keep it in order? > #include <linux/acpi.h> > #include <linux/irqdomain.h> > #include <linux/pm_runtime.h> > +#include

On Mon, Jan 22, 2018 at 8:12 AM, Jan Kiszka <jan.kiszka at siemens.com> wrote: > #include <linux/export.h> > #include <linux/pci.h> > #include <asm/pci_x86.h> > +#include <asm/jailhouse_para.h> Keep it in order? > #include <linux/acpi.h> > #include <linux/irqdomain.h> > #include <linux/pm_runtime.h> > +#include

On Wed, 28 Feb 2018, Jan Kiszka wrote: > From: Jan Kiszka <jan.kiszka at siemens.com> > > Per PCIe r4.0, sec 7.5.1.1.9, multi-function devices are required to > have a function 0. Therefore, Linux scans for devices at function 0 > (devfn 0/8/16/...) and only scans for other functions if function 0 > has its Multi-Function Device bit set or ARI or SR-IOV indicate >

On Tue, Jul 28, 2015 at 12:06 PM, Jan Kiszka <jan.kiszka at siemens.com> wrote: > On 2015-07-28 20:22, Andy Lutomirski wrote: >> On Tue, Jul 28, 2015 at 10:17 AM, Jan Kiszka <jan.kiszka at siemens.com> wrote: >>> On 2015-07-28 19:10, Andy Lutomirski wrote: >>>> The trouble is that this is really a property of the bus and not of >>>> the device.

On Tue, Jul 28, 2015 at 12:06 PM, Jan Kiszka <jan.kiszka at siemens.com> wrote: > On 2015-07-28 20:22, Andy Lutomirski wrote: >> On Tue, Jul 28, 2015 at 10:17 AM, Jan Kiszka <jan.kiszka at siemens.com> wrote: >>> On 2015-07-28 19:10, Andy Lutomirski wrote: >>>> The trouble is that this is really a property of the bus and not of >>>> the device.

On 2015-09-03 10:08, Michael S. Tsirkin wrote: > On Tue, Sep 01, 2015 at 06:28:28PM +0200, Jan Kiszka wrote: >> On 2015-09-01 18:02, Michael S. Tsirkin wrote: >>> On Tue, Sep 01, 2015 at 05:34:37PM +0200, Jan Kiszka wrote: >>>> On 2015-09-01 16:34, Michael S. Tsirkin wrote: >>>>> On Tue, Sep 01, 2015 at 04:09:44PM +0200, Jan Kiszka wrote:

On 2015-09-03 10:08, Michael S. Tsirkin wrote: > On Tue, Sep 01, 2015 at 06:28:28PM +0200, Jan Kiszka wrote: >> On 2015-09-01 18:02, Michael S. Tsirkin wrote: >>> On Tue, Sep 01, 2015 at 05:34:37PM +0200, Jan Kiszka wrote: >>>> On 2015-09-01 16:34, Michael S. Tsirkin wrote: >>>>> On Tue, Sep 01, 2015 at 04:09:44PM +0200, Jan Kiszka wrote:

On Mon, Apr 27, 2015 at 1:55 PM, Jan Kiszka <jan.kiszka at siemens.com> wrote: > Am 2015-04-27 um 14:35 schrieb Jan Kiszka: >> Am 2015-04-27 um 12:17 schrieb Stefan Hajnoczi: >>> On Sun, Apr 26, 2015 at 2:24 PM, Luke Gorrie <luke at snabb.co> wrote: >>>> On 24 April 2015 at 15:22, Stefan Hajnoczi <stefanha at gmail.com> wrote: >>>>>

On Mon, Apr 27, 2015 at 1:55 PM, Jan Kiszka <jan.kiszka at siemens.com> wrote: > Am 2015-04-27 um 14:35 schrieb Jan Kiszka: >> Am 2015-04-27 um 12:17 schrieb Stefan Hajnoczi: >>> On Sun, Apr 26, 2015 at 2:24 PM, Luke Gorrie <luke at snabb.co> wrote: >>>> On 24 April 2015 at 15:22, Stefan Hajnoczi <stefanha at gmail.com> wrote: >>>>>

On 2015-09-01 18:02, Michael S. Tsirkin wrote: > On Tue, Sep 01, 2015 at 05:34:37PM +0200, Jan Kiszka wrote: >> On 2015-09-01 16:34, Michael S. Tsirkin wrote: >>> On Tue, Sep 01, 2015 at 04:09:44PM +0200, Jan Kiszka wrote: >>>> On 2015-09-01 11:24, Michael S. Tsirkin wrote: >>>>> On Tue, Sep 01, 2015 at 11:11:52AM +0200, Jan Kiszka wrote:

On 2015-09-01 18:02, Michael S. Tsirkin wrote: > On Tue, Sep 01, 2015 at 05:34:37PM +0200, Jan Kiszka wrote: >> On 2015-09-01 16:34, Michael S. Tsirkin wrote: >>> On Tue, Sep 01, 2015 at 04:09:44PM +0200, Jan Kiszka wrote: >>>> On 2015-09-01 11:24, Michael S. Tsirkin wrote: >>>>> On Tue, Sep 01, 2015 at 11:11:52AM +0200, Jan Kiszka wrote:

On 27 April 2015 at 16:30, Jan Kiszka <jan.kiszka at siemens.com> wrote: > Today, we have posted interrupts to avoid the vm-exit on the target CPU, > but there is nothing yet (to my best knowledge) to avoid the exit on the > sender side (unless we ignore security). That's the same problem with > intra-guest IPIs, BTW. > > For throughput and given NAPI patterns,

On Thu, Mar 1, 2018 at 7:40 AM, Jan Kiszka <jan.kiszka at siemens.com> wrote: > Use the PCI mmconfig base address exported by jailhouse in boot > parameters in order to access the memory mapped PCI configuration space. > --- a/arch/x86/kernel/jailhouse.c > +++ b/arch/x86/kernel/jailhouse.c > @@ -124,6 +124,13 @@ static int __init jailhouse_pci_arch_init(void) >