On 22/07/2016 15:56, Radim Krčmář wrote:
> 2016-07-22 15:52+0200, Auger Eric:
>> On 22/07/2016 15:39, Radim Krčmář wrote:
>>> 2016-07-21 23:10+0200, Auger Eric:
>>>> On 21/07/2016 18:33, Radim Krčmář wrote:
>>>>> 2016-07-18 13:25+, Eric Auger
Hi Radim,
On 22/07/2016 15:39, Radim Krčmář wrote:
> 2016-07-21 23:10+0200, Auger Eric:
>> On 21/07/2016 18:33, Radim Krčmář wrote:
>>> 2016-07-18 13:25+, Eric Auger:
>>>> If the ITS modality is not available, let's simply support MSI
>>>> injection b
On 22/07/2016 16:14, Radim Krčmář wrote:
> 2016-07-22 13:46+, Eric Auger:
>> Up to now, only irqchip routing entries could be set. This patch
>> adds the capability to insert MSI routing entries.
>>
>> For ARM64, let's also increase KVM_MAX_IRQ_ROUTES to 4096: this
>> include SPI irqchip
Hi Radim
On 22/07/2016 16:24, Radim Krčmář wrote:
> 2016-07-22 13:46+, Eric Auger:
>> This patch adds compilation and link against irqchip.
>>
>> Main motivation behind using irqchip code is to enable MSI
>> routing code. In the future irqchip routing may also be useful
>> when targeting
Hi,
On 22/07/2016 17:40, Marc Zyngier wrote:
> On 22/07/16 15:35, Andrew Jones wrote:
>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>> Hi Stefan,
>>>
>>> On 22/07/16 06:57, Stefan Agner wrote:
Hi,
I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and
Hi Dennis,
On 20/07/2016 13:43, Dennis Chen wrote:
> Hi Eric,
> Some small questions/comments below:
>
> On Tue, Jul 19, 2016 at 12:55:07PM +, Eric Auger wrote:
>> iommu_get/put_msi_cookie allocates/frees the resource used to store
>> and ref count the MSI doorbell mappings.
Hi Radim,
On 21/07/2016 18:33, Radim Krčmář wrote:
> 2016-07-18 13:25+, Eric Auger:
>> If the ITS modality is not available, let's simply support MSI
>> injection by transforming the MSI.data into an SPI ID.
>>
>> This becomes possible to use KVM_SIGNAL_MSI ioctl and MSI
>> routing for arm
Hi,
On 21/07/2016 19:15, Radim Krčmář wrote:
> 2016-07-21 17:43+0100, Andre Przywara:
>> Hi Radim,
>>
>> On 21/07/16 17:01, Radim Krčmář wrote:
>>> 2016-07-18 13:25+, Eric Auger:
On ARM, the MSI msg (address and data) comes along with
out-of-band device ID information. The device ID
Hi Radim,
On 21/07/2016 18:21, Radim Krčmář wrote:
> 2016-07-18 13:25+, Eric Auger:
>> Up to now, only irqchip routing entries could be set. This patch
>> adds the capability to insert MSI routing entries.
>>
>> For ARM64, let's also increase KVM_MAX_IRQ_ROUTES to 4096: this
>> include SPI
Hi,
On 21/07/2016 19:25, Marc Zyngier wrote:
> On 21/07/16 18:22, Radim Krčmář wrote:
>> 2016-07-21 17:54+0100, Marc Zyngier:
>>> On 21/07/16 17:13, Radim Krčmář wrote:
2016-07-18 13:25+, Eric Auger:
> Extend kvm_kernel_irq_routing_entry to transport the device id
> field, devid.
Hi Marc,
On 22/07/2016 09:47, Marc Zyngier wrote:
> Hi Stefan,
>
> On 22/07/16 06:57, Stefan Agner wrote:
>> Hi,
>>
>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>> this stack trace immediately after invoking qemu-system-arm:
>>
>> Unable to handle kernel paging request
Hi Andre,
On 29/07/2016 00:31, André Przywara wrote:
> Hi,
>
> On 22/07/16 17:20, Eric Auger wrote:
>> With the advent of GICv3 ITS in-kernel emulation, KVM MSI routing
>> becomes mandated for proper VIRTIO-PCI vhost integration.
>>
>> In QEMU, when the VIRTIO-PCI device is programmed with the
Hi Thomas,
On 26/07/2016 11:00, Thomas Gleixner wrote:
> B1;2802;0cEric,
>
> On Mon, 25 Jul 2016, Auger Eric wrote:
>> On 20/07/2016 11:04, Thomas Gleixner wrote:
>>> On Tue, 19 Jul 2016, Eric Auger wrote:
>>>> + if (ret) {
>
Hi Thomas,
On 20/07/2016 11:04, Thomas Gleixner wrote:
> On Tue, 19 Jul 2016, Eric Auger wrote:
>> /**
>> + * msi_handle_doorbell_mappings: in case the irq data corresponds to an
>> + * MSI that requires iommu mapping, traverse the irq domain hierarchy
>> + * to retrieve the doorbells to handle
Hi Thomas,
On 20/07/2016 11:09, Thomas Gleixner wrote:
> On Tue, 19 Jul 2016, Eric Auger wrote:
>
> First of all - valid for all patches:
>
> Subject: sys/subsys: Sentence starts with an uppercase letter
OK understood.
>
> Now for this particular one:
>
> genirq/msi: use the MSI doorbell's
Hi,
On 24/07/2016 03:41, kbuild test robot wrote:
> Hi,
>
> [auto build test ERROR on vfio/next]
> [also build test ERROR on v4.7-rc7 next-20160722]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
>
On 03/08/2016 19:56, Auger Eric wrote:
> Hi
>
> On 03/08/2016 19:48, Auger Eric wrote:
>> Hi Andre, Christoffer,
>>
>> On 03/08/2016 19:18, Andre Przywara wrote:
>>> Hi,
>>>
>>> On 03/08/16 18:11, Christoffer Dall wrote:
>>>&
Hi Andre, Christoffer,
On 03/08/2016 19:18, Andre Przywara wrote:
> Hi,
>
> On 03/08/16 18:11, Christoffer Dall wrote:
>> On Wed, Aug 03, 2016 at 03:57:45PM +0100, Andre Przywara wrote:
>>> Currently we register ITS devices upon userland issuing the CTRL_INIT
>>> ioctl to mark initialization of
Hi
On 03/08/2016 19:48, Auger Eric wrote:
> Hi Andre, Christoffer,
>
> On 03/08/2016 19:18, Andre Przywara wrote:
>> Hi,
>>
>> On 03/08/16 18:11, Christoffer Dall wrote:
>>> On Wed, Aug 03, 2016 at 03:57:45PM +0100, Andre Przywara wrote:
>>>>
Hi Andre,
On 04/08/2016 12:17, Andre Przywara wrote:
> Hi Eric,
>
> On 04/08/16 11:11, Auger Eric wrote:
>> Hi Andre,
>>
>> On 03/08/2016 16:57, Andre Przywara wrote:
>>> Currently we register ITS devices upon userland issuing the CTRL_INIT
>>> io
Hi Andre,
On 03/08/2016 16:57, Andre Przywara wrote:
> Currently we register ITS devices upon userland issuing the CTRL_INIT
> ioctl to mark initialization of the ITS as done.
> This deviates from the initialization sequence of the existing GIC
> devices and does not play well with the way QEMU
Hi Andre,
On 11/07/2016 18:25, Andre Przywara wrote:
> Hi Eric,
>
> On 06/07/16 09:47, Eric Auger wrote:
>> This patch adds compilation and link against irqchip.
>>
>> Main motivation behind using irqchip code is to enable MSI
>> routing code. In the future irqchip routing may also be useful
>>
Hi Drew, Radim,
On 08/07/2016 22:55, Radim Krčmář wrote:
> 2016-07-08 10:52+0200, Andrew Jones:
>> On Fri, Jul 08, 2016 at 10:16:53AM +0200, Auger Eric wrote:
>>> On 07/07/2016 19:20, Andrew Jones wrote:
>>>> On Wed, Jul 06, 2016 at 10:47:53AM +0200, Eric Auger wrot
Hi Andre,
On 11/07/2016 18:26, Andre Przywara wrote:
> Hi,
>
> On 06/07/16 09:47, Eric Auger wrote:
>> If the ITS modality is not available, let's simply support MSI
>> injection by transforming the MSI.data into an SPI ID.
>>
>> This becomes possible to use KVM_SIGNAL_MSI ioctl and MSI
>>
Hi,
On 20/07/2016 10:12, Thomas Gleixner wrote:
> On Tue, 19 Jul 2016, Eric Auger wrote:
>> +bool msi_doorbell_safe(void)
>> +{
>> +struct irqchip_doorbell *db;
>> +bool irq_remapping = true;
>> +
>> +mutex_lock(_doorbell_mutex);
>> +list_for_each_entry(db, _doorbell_list, next) {
Hi Thomas,
On 19/07/2016 16:38, Thomas Gleixner wrote:
> On Tue, 19 Jul 2016, Eric Auger wrote:
>> msi_doorbell_pages sum up the number of iommu pages of a given order
>
> adding () to the function name would make it immediately clear that
> msi_doorbell_pages is a function.
>
>> +/**
>> + *
Hi Andre,
On 15/07/2016 13:43, Andre Przywara wrote:
> Hi,
>
> this series allows those KVM guests that use an emulated GICv3 to use LPIs
> as well, though in the moment this is limited to emulated PCI devices.
> This is based on kvmarm/queue, which now only features the new VGIC
>
Hi Andre,
On 18/07/2016 18:34, Andre Przywara wrote:
> Hi Eric,
>
> On 18/07/16 10:18, Auger Eric wrote:
>> Hi Andre, Marc,
>>
>> On 15/07/2016 13:43, Andre Przywara wrote:
>>> The ARM GICv3 ITS emulation code goes into a separate file, but needs
>&g
Hi Dennis
On 20/07/2016 11:56, Dennis Chen wrote:
> Hi Eric,
>
> On Tue, Jul 19, 2016 at 12:55:03PM +, Eric Auger wrote:
>> This series introduces the msi-iommu api used to:
>>
>> - allocate/free resources for MSI IOMMU mapping
>> - set the MSI iova window aperture
>> - map/unmap physical
Hi Marc,
On 19/07/2016 18:16, Marc Zyngier wrote:
> On 19/07/16 16:46, Paolo Bonzini wrote:
>>
>>
>> On 19/07/2016 16:56, Marc Zyngier wrote:
>>> On 18/07/16 14:25, Eric Auger wrote:
This patch adds compilation and link against irqchip.
Main motivation behind using irqchip code is
Hi Thomas,
On 19/07/2016 16:38, Thomas Gleixner wrote:
> On Tue, 19 Jul 2016, Eric Auger wrote:
>> msi_doorbell_pages sum up the number of iommu pages of a given order
>
> adding () to the function name would make it immediately clear that
> msi_doorbell_pages is a function.
>
>> +/**
>> + *
Hi Thomas,
On 19/07/2016 16:22, Thomas Gleixner wrote:
> On Tue, 19 Jul 2016, Eric Auger wrote:
>> +
>> +#include
>> +#include
>> +#include
>> +
>> +struct irqchip_doorbell {
>> +struct irq_chip_msi_doorbell_info info;
>> +struct list_head next;
>
> Again, please align the struct
Hi Andre, Marc,
On 15/07/2016 13:43, Andre Przywara wrote:
> The ARM GICv3 ITS emulation code goes into a separate file, but needs
> to be connected to the GICv3 emulation, of which it is an option.
> The ITS MMIO handlers require the respective ITS pointer to be passed in,
> so we amend the
Hi,
On 18/07/2016 11:43, Marc Zyngier wrote:
> On 18/07/16 10:18, Auger Eric wrote:
>> Hi Andre, Marc,
>>
>> On 15/07/2016 13:43, Andre Przywara wrote:
>>> The ARM GICv3 ITS emulation code goes into a separate file, but needs
>>> to be connected to the GI
Hi Andre,
On 04/07/2016 19:40, Andre Przywara wrote:
> Hi Eric,
>
> On 04/07/16 16:00, Auger Eric wrote:
>> Hi Peter,
>>
>> On 04/07/2016 16:32, Peter Maydell wrote:
>>> On 4 July 2016 at 15:27, Auger Eric <eric.au...@redhat.com> wrote:
>>>>
Hi Andre,
On 04/07/2016 19:40, Andre Przywara wrote:
> Hi Eric,
>
> On 04/07/16 16:00, Auger Eric wrote:
>> Hi Peter,
>>
>> On 04/07/2016 16:32, Peter Maydell wrote:
>>> On 4 July 2016 at 15:27, Auger Eric <eric.au...@redhat.com> wrote:
>>>>
On 05/07/2016 10:59, Andre Przywara wrote:
> Hi Eric,
>
> thank you very much for the elaborate explanation!
>
> On 05/07/16 08:40, Auger Eric wrote:
>> Hi Andre,
>> On 04/07/2016 19:40, Andre Przywara wrote:
>>> Hi Eric,
>>>
>>&
Hi Andre,
On 05/07/2016 15:50, Andre Przywara wrote:
> kvm_vgic_early_init() and kvm_vgic_vcpu_early_init() were only used
> with the old VGIC, on the new VGIC these functions do nothing.
> Follow the comment in vgic-init.c and remove those functions and
> their calls.
>
> Signed-off-by: Andre
Hi Drew,
On 07/07/2016 19:20, Andrew Jones wrote:
> On Wed, Jul 06, 2016 at 10:47:53AM +0200, Eric Auger wrote:
>> This patch adds compilation and link against irqchip.
>>
>> Main motivation behind using irqchip code is to enable MSI
>> routing code. In the future irqchip routing may also be
On 04/07/2016 16:00, Andre Przywara wrote:
> Hi,
>
> On 04/07/16 14:54, Auger Eric wrote:
>> Hi Andre,
>>
>> On 04/07/2016 15:38, Andre Przywara wrote:
>>> 2) on KVM_DEV_ARM_VGIC_GRP_ADDR check that "initialized" is false
>>> 3) on KVM_D
Andre,
On 04/07/2016 16:05, Andre Przywara wrote:
> Hi,
>
> On 04/07/16 10:00, Auger Eric wrote:
>> Hi Andre,
>>
>> On 28/06/2016 14:32, Andre Przywara wrote:
>>> Introduce a new KVM device that represents an ARM Interrupt Translation
>>> Service
Hi Peter,
On 04/07/2016 16:32, Peter Maydell wrote:
> On 4 July 2016 at 15:27, Auger Eric <eric.au...@redhat.com> wrote:
>> Andre,
>>
>> On 04/07/2016 16:05, Andre Przywara wrote:
>>> Hi,
>>>
>>> On 04/07/16 10:00, Auger Eric wrote:
>>
Hi Andre,
On 05/07/2016 13:22, Andre Przywara wrote:
> Hi,
>
> this series allows those KVM guests that use an emulated GICv3 to use LPIs
> as well, though in the moment this is limited to emulated PCI devices.
> This is based on kvmarm/queue, which now only features the new VGIC
>
Hi Andre,
On 08/08/2016 17:45, Andre Przywara wrote:
> Currently we register an ITS device upon userland issuing the CTLR_INIT
> ioctl to mark initialization of the ITS as done.
> This deviates from the initialization sequence of the existing GIC
> devices and does not play well with the way QEMU
Hi,
On 30/06/2016 13:40, Andrew Jones wrote:
> On Thu, Jun 30, 2016 at 11:09:30AM +0100, Andre Przywara wrote:
>> Hi,
>>
>> On 29/06/16 05:43, Bharat Bhushan wrote:
>>>
>>>
-Original Message-
From: kvmarm-boun...@lists.cs.columbia.edu [mailto:kvmarm-
Hi Andre,
On 28/06/2016 14:32, Andre Przywara wrote:
> Logically a GICv3 redistributor is assigned to a (v)CPU, so we should
> aim to keep redistributor related variables out of our struct vgic_dist.
>
> Let's start by replacing the redistributor related kvm_io_device array
> with two members in
On 28/06/2016 14:32, Andre Przywara wrote:
> kvm_register_device_ops() can return an error, so lets check its return
returned
> value and propagate this up the call chain.
>
> Signed-off-by: Andre Przywara
> ---
> virt/kvm/arm/vgic/vgic-kvm-device.c | 15
On 28/06/2016 14:32, Andre Przywara wrote:
> The kvm_io_bus framework is a nice place of holding information about
> various MMIO regions for kernel emulated devices.
> Add a call to retrieve the kvm_io_device structure which is associated
> with a certain MMIO address. This avoids to duplicate
Hi Andre,
On 28/06/2016 14:32, Andre Przywara wrote:
> In the moment our struct vgic_irq's are statically allocated at guest
> creation time. So getting a pointer to an IRQ structure is trivial and
> safe. LPIs are more dynamic, they can be mapped and unmapped at any time
> during the guest's
Hi Andre,
On 28/06/2016 14:32, Andre Przywara wrote:
> In the GICv3 redistributor there are the PENDBASER and PROPBASER
> registers which we did not emulate so far, as they only make sense
> when having an ITS. In preparation for that emulate those MMIO
> accesses by storing the 64-bit data
Hi Andre,
On 28/06/2016 14:32, Andre Przywara wrote:
> Now that all ITS emulation functionality is in place, we advertise
> MSI functionality to userland and also the ITS device to the guest - if
> userland has configured that.
>
> Signed-off-by: Andre Przywara
> ---
>
Hi Linu,
On 11/01/2017 17:52, linucher...@gmail.com wrote:
> From: Linu Cherian
>
> Having only 32 memslots is a real constraint for the maximum number of
> PCI devices that can be assigned to a single guest. Assuming each PCI
> device/virtual function having two memory
Hi Christoffer,
On 24/01/2017 14:25, Christoffer Dall wrote:
> Add a file to debugfs to read the in-kernel state of the vgic. We don't
> do any locking of the entire VGIC state while traversing all the IRQs,
> so if the VM is running the user/developer may not see a quiesced state,
> but should
Hi,
On 26/01/2017 15:20, vijay.kil...@gmail.com wrote:
> From: Vijaya Kumar K
>
> Read and write of some registers like ISPENDR and ICPENDR
> from userspace requires special handling when compared to
> guest access for these registers.
>
> Refer to
Hi,
On 26/01/2017 15:20, vijay.kil...@gmail.com wrote:
> From: Vijaya Kumar K
>
> VGICv3 Distributor and Redistributor registers are accessed using
> KVM_DEV_ARM_VGIC_GRP_DIST_REGS and KVM_DEV_ARM_VGIC_GRP_REDIST_REGS
> with KVM_SET_DEVICE_ATTR and KVM_GET_DEVICE_ATTR
Hi,
On 26/01/2017 15:20, vijay.kil...@gmail.com wrote:
> From: Vijaya Kumar K
>
> ICC_VMCR_EL2 supports virtual access to ICC_IGRPEN1_EL1.Enable
> and ICC_IGRPEN0_EL1.Enable fields. Add grpen0 and grpen1 member
> variables to struct vmcr to support read and write of
Hi,
On 26/01/2017 15:20, vijay.kil...@gmail.com wrote:
> From: Vijaya Kumar K
>
> VGICv3 CPU interface registers are accessed using
> KVM_DEV_ARM_VGIC_CPU_SYSREGS ioctl. These registers are accessed
> as 64-bit. The cpu MPIDR value is passed along with register id.
> It
Hi,
On 26/01/2017 15:20, vijay.kil...@gmail.com wrote:
> From: Vijaya Kumar K
>
> Userspace requires to store and restore of line_level for
> level triggered interrupts using ioctl KVM_DEV_ARM_VGIC_GRP_LEVEL_INFO.
>
> Signed-off-by: Vijaya Kumar K
Hi,
On 27/01/2017 09:32, Auger Eric wrote:
> Hi,
>
> On 26/01/2017 15:20, vijay.kil...@gmail.com wrote:
>> From: Vijaya Kumar K <vijaya.ku...@cavium.com>
>>
>> Userspace requires to store and restore of line_level for
>> level triggered interrupts usin
Hi Vijaya,
On 26/01/2017 15:20, vijay.kil...@gmail.com wrote:
> From: Vijaya Kumar K
>
> Update error code returned for Invalid CPU interface register
> value and access in AArch32 mode.
>
> Signed-off-by: Vijaya Kumar K
Reviewed-by: Eric
Hi Vijaya,
On 26/01/2017 15:20, vijay.kil...@gmail.com wrote:
> From: Vijaya Kumar K
>
> This patchset adds API for saving and restoring
> of VGICv3 registers to support live migration with new vgic feature.
> This API definition is as per version of VGICv3
Hi Marc,
On 13/01/2017 10:46, Marc Zyngier wrote:
> On 13/01/17 09:07, Auger Eric wrote:
>> Hi Marc,
>>
>> On 12/01/2017 17:52, Marc Zyngier wrote:
>>> Hi Eric,
>>>
>>> On 12/01/17 15:56, Eric Auger wrote:
>>>> Add description for how
On 17/01/2017 11:20, Marc Zyngier wrote:
> Most ITS commands do operate on a collection object, and require
> a SYNC command to be performed on that collection in order to
> guarantee the execution of the first command.
>
> With GICv4 ITS, another set of commands perform similar operations
> on
On 17/01/2017 11:20, Marc Zyngier wrote:
> Allow the pending state of an LPI to be set or cleared via
> irq_set_irqchip_state.
>
> Signed-off-by: Marc Zyngier
Reviewed-by: Eric Auger
Eric
> ---
> drivers/irqchip/irq-gic-v3-its.c | 78
>
Hi Marc,
On 17/01/2017 11:20, Marc Zyngier wrote:
> Move the LPI property table allocation into its own function, as
> this is going to be required for those associated with VMs in
> the future.
>
> Signed-off-by: Marc Zyngier
> ---
> drivers/irqchip/irq-gic-v3-its.c | 28
Hi Marc,
On 17/01/2017 11:20, Marc Zyngier wrote:
> The VCPU tables can be quite sparse as well, and it makes sense
> to use indirect tables as well if possible.
>
> Signed-off-by: Marc Zyngier
> ---
> drivers/irqchip/irq-gic-v3-its.c | 20 +---
> 1 file
Hi Marc,
On 22/02/2017 13:13, Marc Zyngier wrote:
> Our GICv3 emulation always presents ICC_SRE_EL1 with DIB/DFB set to
> zero, which implies that there is a way to bypass the GIC and
> inject raw IRQ/FIQ by driving the CPU pins.
>
> Of course, we don't allow that when the GIC is configured, but
Hi Andre,
On 10/02/2017 18:06, Andre Przywara wrote:
> Hi,
>
> On 10/02/17 12:26, Auger Eric wrote:
>> Hi Andre,
>>
>> On 10/02/2017 12:57, Andre Przywara wrote:
>>> On 08/02/17 11:43, Eric Auger wrote:
>>>
>>> Salut Eric,
>>>
>
Hi Andre,
On 10/02/2017 12:57, Andre Przywara wrote:
> On 08/02/17 11:43, Eric Auger wrote:
>
> Salut Eric,
>
> one minor thing below, but first a general question:
> I take it that the state of the ITS (enabled/disabled) shouldn't matter
> when it comes to reading/writing registers, right?
Hi,
On 17/01/2017 11:20, Marc Zyngier wrote:
> Add helper functions that probe for VLPI and DirectLPI properties.
>
> Signed-off-by: Marc Zyngier
Besides the returned value previous questions,
Reviewed-by: Eric Auger
Eric
> ---
>
On 17/01/2017 11:20, Marc Zyngier wrote:
> The way we encode the various ITS command fields is both tedious
> and error prone. Let's introduce a helper function that performs
> the encoding, and convert the existing encoders to use that
> helper.
>
> Signed-off-by: Marc Zyngier
Hi Marc,
On 17/01/2017 11:20, Marc Zyngier wrote:
> The various LPI definitions are in the middle of the code, and
> would be better placed at the beginning, given that we're going
> to use some of them much earlier.
>
> Signed-off-by: Marc Zyngier
Reviewed-by: Eric Auger
Hi,
On 13/02/2017 11:00, Thomas Gleixner wrote:
> On Tue, 17 Jan 2017, Marc Zyngier wrote:
>> +typer = gic_read_typer(its_base + GITS_TYPER);
>> its->base = its_base;
>> its->phys_base = res->start;
>> -its->ite_size = ((gic_read_typer(its_base + GITS_TYPER) >> 4) & 0xf) +
>>
Hi Marc,
On 17/01/2017 11:20, Marc Zyngier wrote:
> In order to discover the VLPI properties, we need to iterate over
> the redistributor regions. As we already have code that does this,
> let's factor it out and make it slightly more generic.
>
> Signed-off-by: Marc Zyngier
Hi Andre,
On 16/02/2017 11:41, Andre Przywara wrote:
> The ITS spec says that ITS commands are only processed when the ITS
> is enabled (section 8.19.4, Enabled, bit[0]). Our emulation was not taking
> this into account.
> Fix this by checking the enabled state before handling CWRITER writes.
Marc,
On 17/01/2017 11:20, Marc Zyngier wrote:
> Allow the pending state of an LPI to be set or cleared via
> irq_set_irqchip_state.
>
> Signed-off-by: Marc Zyngier
Reviewed-by: Eric Auger
Eric
> ---
> drivers/irqchip/irq-gic-v3-its.c | 78
>
Hi,
On 17/01/2017 11:20, Marc Zyngier wrote:
> Most ITS commands do operate on a collection object, and require
> a SYNC command to be performed on that collection in order to
> guarantee the execution of the first command.
>
> With GICv4 ITS, another set of commands perform similar operations
>
Hi all,
On 08/02/2017 12:43, Eric Auger wrote:
> This patch flushes the device table entries into guest RAM.
> Both flat table and 2 stage tables are supported. DeviceId
> indexing is used.
>
> For each device listed in the device table, we also flush
> the translation table using the
Hi Drew,
On 15/07/2016 15:00, Andrew Jones wrote:
> Signed-off-by: Andrew Jones
>
> ---
> v2: configure irqs as NS GRP1
> ---
> lib/arm/asm/arch_gicv3.h | 184 ++
> lib/arm/asm/gic-v3.h | 321
> +
>
Hi,
On 15/07/2016 15:00, Andrew Jones wrote:
> Reviewed-by: Alex Bennée
> Signed-off-by: Andrew Jones
> ---
> lib/arm/asm/processor.h | 10 ++
> lib/arm64/asm/processor.h | 10 ++
> 2 files changed, 20 insertions(+)
>
> diff --git
Hi Drew,
On 15/07/2016 15:00, Andrew Jones wrote:
> Allow a thread to wait some specified amount of time. Can
> specify in cycles, usecs, and msecs.
>
> Reviewed-by: Alex Bennée
> Signed-off-by: Andrew Jones
> ---
> lib/arm/asm/processor.h | 19
Hi Drew,
On 15/07/2016 15:00, Andrew Jones wrote:
> Allow user to select who sends ipis and with which irq,
> rather than just always sending irq=0 from cpu0.
>
> Signed-off-by: Andrew Jones
>
> ---
> v2: actually check that the irq received was the irq sent,
> and (for
Hi Drew,
Proper commit message?
... also selects the vgic model corresponding to the host
> Reviewed-by: Alex Bennée
> Signed-off-by: Andrew Jones
> ---
> arm/run | 19 ---
> arm/selftest.c| 5 -
>
Hi Drew,
On 15/07/2016 15:00, Andrew Jones wrote:
> Make implementation equivalent to Linux's include/linux/stringify.h
>
> Signed-off-by: Andrew Jones
> ---
> lib/libcflat.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/libcflat.h
Hi,
On 15/07/2016 15:00, Andrew Jones wrote:
> mrs is always 64bit, so we should always use a 64bit register.
> Sometimes we'll only want to return the lower 32, but not for
> MPIDR, as that does define fields in the upper 32.
>
> Reviewed-by: Alex Bennée
>
Hi Drew,
On 15/07/2016 15:00, Andrew Jones wrote:
> Signed-off-by: Andrew Jones
>
> ---
> v2: use IRM for gicv3 broadcast
> ---
> arm/gic.c | 157
> ++
> arm/unittests.cfg | 6 +++
> 2 files changed, 154
Hi Drew,
On 15/07/2016 15:00, Andrew Jones wrote:
> Signed-off-by: Andrew Jones
> ---
> v2: add more details in the output if a test fails,
> report spurious interrupts if we get them
> ---
> arm/Makefile.common | 6 +-
> arm/gic.c | 194
>
Hi,
On 16/08/2016 19:35, Christoffer Dall wrote:
> Just a rename so we can implement a v3-specific function later.
>
> We take the chance to get rid of the V2/V3 ops comments as well.
>
> No functional change.
>
> Signed-off-by: Christoffer Dall
> ---
>
Hi Christoffer,
On 16/08/2016 19:35, Christoffer Dall wrote:
> As we are about to deal with multiple data types and situations where
> the vgic should not be initialized when doing userspace accesses on the
> register attributes, factor out the functionality of
> vgic_attr_regs_access into
Hi,
On 14/11/2016 22:08, Andrew Jones wrote:
> Allow user to select who sends ipis and with which irq,
> rather than just always sending irq=0 from cpu0.
>From a user point of view is there a way to know the list of available
tests and their arg?
>
> Signed-off-by: Andrew Jones
Hi Drew,
On 14/11/2016 22:08, Andrew Jones wrote:
> Reviewed-by: Alex Bennée
> Signed-off-by: Andrew Jones
>
> ---
> v6:
> - added comments [Alex]
> - added stride parameter to gicv3_set_redist_base [Andre]
> - redist-wait s/rwp/uwp/ and comment
Hi,
On 14/11/2016 22:08, Andrew Jones wrote:
> From: Peter Xu
>
> These macros will be useful to do page alignment checks.
>
> Reviewed-by: Andre Przywara
> Signed-off-by: Peter Xu
> [drew: also added SZ_64K and changed to shifts]
Hi,
On 14/11/2016 22:08, Andrew Jones wrote:
> Add some gicv2 support. This just adds init and enable
> functions, allowing unit tests to start messing with it.
>
> Reviewed-by: Andre Przywara
> Signed-off-by: Andrew Jones
>
> ---
> v6: added
Hi Andre,
On 23/11/2016 14:24, Auger Eric wrote:
> Hi,
>
> On 18/11/2016 15:20, Andrew Jones wrote:
>> On Thu, Nov 17, 2016 at 05:57:51PM +, Andre Przywara wrote:
>>> Some tests for the ITARGETS registers.
>>> Bits corresponding to non-existent CPUs must be
On 23/11/2016 14:01, Andrew Jones wrote:
> On Wed, Nov 23, 2016 at 12:28:34PM +0100, Auger Eric wrote:
>> Hi,
>>
>> On 14/11/2016 22:08, Andrew Jones wrote:
>>> Allow user to select who sends ipis and with which irq,
>>> rather than just always sendin
Hi Andre,
On 18/11/2016 15:02, Andrew Jones wrote:
> On Thu, Nov 17, 2016 at 05:57:50PM +, Andre Przywara wrote:
>> Some tests for the IPRIORITY registers. The significant number of bits
>> is IMPLEMENTATION DEFINED, but should be the same for every IRQ.
>> Also these registers must be
Hi,
On 18/11/2016 15:20, Andrew Jones wrote:
> On Thu, Nov 17, 2016 at 05:57:51PM +, Andre Przywara wrote:
>> Some tests for the ITARGETS registers.
>> Bits corresponding to non-existent CPUs must be RAZ/WI.
>> These registers must be byte-accessible, also check that accesses beyond
>> the
Hi Drew,
On 23/11/2016 17:54, Andrew Jones wrote:
> Reviewed-by: Alex Bennée
> Reviewed-by: Eric Auger
> Signed-off-by: Andrew Jones
>
> ---
> v7: split lib/arm/gic.c into gic-v2/3.c [Eric]
> v6:
> - added comments [Alex]
>
Hi,
On 23/11/2016 17:54, Andrew Jones wrote:
> Allow user to select who sends ipis and with which irq,
> rather than just always sending irq=0 from cpu0.
>
> Signed-off-by: Andrew Jones
Reviewed-by: Eric Auger
Tested-by: Eric Auger
Hi Drew,
On 24/11/2016 15:11, Andrew Jones wrote:
> On Thu, Nov 24, 2016 at 10:57:01AM +0100, Auger Eric wrote:
>> Hi,
>>
>> On 23/11/2016 17:54, Andrew Jones wrote:
>>> Allow user to select who sends ipis and with which irq,
>>> rather than just always send
1 - 100 of 812 matches
Mail list logo