Michael Ellerman [mich...@ellerman.id.au] wrote:
| On Tue, Oct 01, 2013 at 05:15:07PM -0700, Sukadev Bhattiprolu wrote:
| > perf_mem_data_src is an union that is initialized via the ->val field
| > and accessed via the bitmap fields. For this to work on big endian
| > platforms, we also need a big-
On 10/05/2013 11:52 AM, Alexey Kardashevskiy wrote:
> On 05.10.2013 2:05, Alex Williamson wrote:
>> On Fri, 2013-10-04 at 22:24 +1000, Alexey Kardashevskiy wrote:
>>> This is a very rough change set required for ppc64 to use this KVM device.
>>>
>>> vfio_rm.c is a piece of code which is going to be
On 05.10.2013 2:05, Alex Williamson wrote:
> On Fri, 2013-10-04 at 22:24 +1000, Alexey Kardashevskiy wrote:
>> This is a very rough change set required for ppc64 to use this KVM device.
>>
>> vfio_rm.c is a piece of code which is going to be called from the realmode
>> (MMU off),
>> and I will put
On 05.10.2013, at 01:45, Paul Mackerras wrote:
> On Fri, Oct 04, 2013 at 03:00:11PM +0200, Alexander Graf wrote:
>>
>> On 04.10.2013, at 14:35, Paul Mackerras wrote:
>>
>>> On Fri, Oct 04, 2013 at 02:27:02PM +0200, Alexander Graf wrote:
On 04.10.2013, at 14:23, Alexander Graf wrote:
On Fri, Oct 04, 2013 at 03:00:11PM +0200, Alexander Graf wrote:
>
> On 04.10.2013, at 14:35, Paul Mackerras wrote:
>
> > On Fri, Oct 04, 2013 at 02:27:02PM +0200, Alexander Graf wrote:
> >>
> >> On 04.10.2013, at 14:23, Alexander Graf wrote:
> >>
> >>>
> >>> On 03.10.2013, at 06:14, Paul Macke
On Fri, 2013-10-04 at 10:29 +0200, Alexander Gordeev wrote:
> On Thu, Oct 03, 2013 at 11:49:45PM +0100, Ben Hutchings wrote:
> > On Wed, 2013-10-02 at 12:48 +0200, Alexander Gordeev wrote:
> > > This update converts pci_enable_msix() and pci_enable_msi_block()
> > > interfaces to canonical kernel f
On Fri, Oct 4, 2013 at 12:51 AM, Ingo Molnar wrote:
>> +static void bpf_jit_free_deferred(struct work_struct *work)
>> +{
>> + struct sk_filter *fp = container_of((void *)work, struct sk_filter,
>> + insns);
>> + unsigned long addr = (unsigned long)f
Hi all,
We are several Openwrt users based on the TPlink 4900 device and suffer from a
crashing gianfar driver.
We troubleshooted the problem down to the fact, that a 3.8er Linux kernel is
working, and a v3.10 crashes, but there is
no reproducable case yet. The driver crashes after a couple of m
Hi all,
We are several Openwrt users based on the TPlink 4900 device and suffer from a
crashing gianfar driver.
We troubleshooted the problem down to the fact, that a 3.8er Linux kernel is
working, and a v3.10 crashes, but there is
no reproducable case yet. The driver crashes after a couple of m
on x86 system with net.core.bpf_jit_enable = 1
sudo tcpdump -i eth1 'tcp port 22'
causes the warning:
[ 56.766097] Possible unsafe locking scenario:
[ 56.766097]
[ 56.780146]CPU0
[ 56.786807]
[ 56.793188] lock(&(&vb->lock)->rlock);
[ 56.799593]
[ 56.805889]
on x86 system with net.core.bpf_jit_enable = 1
sudo tcpdump -i eth1 'tcp port 22'
causes the warning:
[ 56.766097] Possible unsafe locking scenario:
[ 56.766097]
[ 56.780146]CPU0
[ 56.786807]
[ 56.793188] lock(&(&vb->lock)->rlock);
[ 56.799593]
[ 56.805889]
on x86 system with net.core.bpf_jit_enable = 1
sudo tcpdump -i eth1 'tcp port 22'
causes the warning:
[ 56.766097] Possible unsafe locking scenario:
[ 56.766097]
[ 56.780146]CPU0
[ 56.786807]
[ 56.793188] lock(&(&vb->lock)->rlock);
[ 56.799593]
[ 56.805889]
On Wed, 2 Oct 2013 12:49:07 +0200
Alexander Gordeev wrote:
> Subject: [PATCH RFC 51/77] mthca: Update MSI/MSI-X interrupts
> enablement code Date: Wed, 2 Oct 2013 12:49:07 +0200
> Sender: linux-rdma-ow...@vger.kernel.org
> X-Mailer: git-send-email 1.7.7.6
>
> As result of recent re-design of t
On Thu, Oct 03, 2013 at 10:46:21PM +0100, Ben Hutchings wrote:
> On Wed, 2013-10-02 at 17:39 -0700, Jon Mason wrote:
> > On Wed, Oct 02, 2013 at 12:48:17PM +0200, Alexander Gordeev wrote:
> > > Signed-off-by: Alexander Gordeev
> >
> > Since you are changing the behavior of the msix_capability_ini
Hi,
I've been trying to track down a performance regression that started
leading up to the v3.6 kernel, and while doing this I've been
gathering perf data on v3.6-rc and comparing it to v3.11 perf reports
of the same workload.
With v3.6-rc kernels I get all symbols resolved like this:
# Events:
On Wed, 2 Oct 2013 12:49:02 +0200
Alexander Gordeev wrote:
> As result of recent re-design of the MSI/MSI-X interrupts enabling
> pattern this driver has to be updated to use the new technique to
> obtain a optimal number of MSI/MSI-X interrupts required.
>
> Signed-off-by: Alexander Gordeev
On Wed, 2 Oct 2013 12:49:02 +0200
Alexander Gordeev wrote:
UPDATING THIS REPLY.
Your change log confused me. The change below is not from a "recent
re-design", it is required due to an earlier patch in this patch set.
>From the log, I assumed that the change you are talking about is already
upst
On Wed, 2 Oct 2013 12:49:02 +0200
Alexander Gordeev wrote:
NACK. This change does not do anything logically as far as I can tell.
pci_enable_msix in the current upstream kernel itself calls
pci_msix_table_size. The current code yields the same results
as the code suggested below. (i.e., the su
On Wed, Oct 02, 2013 at 12:49:11PM +0200, Alexander Gordeev wrote:
> As result of recent re-design of the MSI/MSI-X interrupts enabling
> pattern this driver has to be updated to use the new technique to
> obtain a optimal number of MSI/MSI-X interrupts required.
>
> Signed-off-by: Alexander Gorde
On Thu, Oct 3, 2013 at 10:16 PM, Eric Dumazet wrote:
> On Thu, 2013-10-03 at 21:11 -0700, Alexei Starovoitov wrote:
>
> -static inline unsigned int sk_filter_len(const struct sk_filter *fp)
> +static inline unsigned int sk_filter_size(const struct sk_filter *fp,
> +
Hello,
Yes the driver owner exist. We have a proposal of l2 switch bindings.
Will send a patch with the l2 switch bindings added on top of existing T104x
proposal.
Regards,
Bogdan V
-Original Message-
From: Linuxppc-dev
[mailto:linuxppc-dev-bounces+bogdan.vlad=freescale@lists.ozlab
On Wed, Oct 02, 2013 at 12:49:09PM +0200, Alexander Gordeev wrote:
> Current MSI-X enablement code assumes MSI-Xs were successfully
> allocated in case less than requested vectors were available.
> That assumption is wrong, since MSI-Xs should be enabled with
> a repeated call to pci_enable_msix().
On Wed, Oct 02, 2013 at 12:48:17PM +0200, Alexander Gordeev wrote:
> Signed-off-by: Alexander Gordeev
Since you are changing the behavior of the msix_capability_init
function on populate_msi_sysfs error, a comment describing why in this
commit would be nice.
> ---
> drivers/pci/msi.c | 11 +++
On Wed, Oct 02, 2013 at 12:49:33PM +0200, Alexander Gordeev wrote:
> As result of recent re-design of the MSI/MSI-X interrupts enabling
> pattern this driver has to be updated to use the new technique to
> obtain a optimal number of MSI/MSI-X interrupts required.
>
> Signed-off-by: Alexander Gorde
On Wed, Oct 02, 2013 at 12:49:10PM +0200, Alexander Gordeev wrote:
> Signed-off-by: Alexander Gordeev
> ---
> drivers/ntb/ntb_hw.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/ntb/ntb_hw.c b/drivers/ntb/ntb_hw.c
> index de2062c..eccd5e5 100644
> --- a/dr
On Wed, 2013-10-02 at 12:48 +0200, Alexander Gordeev wrote:
> As result of recent re-design of the MSI/MSI-X interrupts enabling
> pattern this driver has to be updated to use the new technique to
> obtain a optimal number of MSI/MSI-X interrupts required.
>
> Signed-off-by: Alexander Gordeev
> -
On 09/19/2013 11:44 PM, Russell King wrote:
> Replace the following sequence:
>
> dma_set_mask(dev, mask);
> dma_set_coherent_mask(dev, mask);
>
> with a call to the new helper dma_set_mask_and_coherent().
>
> Signed-off-by: Russell King
Acked-by: Hans Verkuil
Regards,
H
On 10/02/2013 04:04 AM, Joe Perches wrote:
Convert the memset/memcpy uses of 6 to ETH_ALEN
where appropriate.
Also convert some struct definitions and u8 array
declarations of [6] to ETH_ALEN.
For brcmsmac
Acked-by: Arend van Spriel
Signed-off-by: Joe Perches
---
drivers/net/wireless/brc
On Fri, 2013-10-04 at 17:23 +, Bhushan Bharat-R65777 wrote:
>
> > -Original Message-
> > From: Alex Williamson [mailto:alex.william...@redhat.com]
> > Sent: Friday, October 04, 2013 10:43 PM
> > To: Bhushan Bharat-R65777
> > Cc: j...@8bytes.org; b...@kernel.crashing.org; ga...@kernel.c
* Alexei Starovoitov wrote:
> >> #else
> >> +#include
> >
> > Inlines in the middle of header files are generally frowned upon.
> >
> > The standard pattern is to put them at the top, that way it's easier to
> > see the dependencies and there's also less .config dependent inclusion,
> > which
* Eric Dumazet wrote:
> 1)
> >
> > I took a brief look at arch/x86/net/bpf_jit_comp.c while reviewing this
> > patch.
> >
> > You need to split up bpf_jit_compile(), it's an obscenely large, ~600
> > lines long function. We don't do that in modern, maintainable kernel code.
> >
> > 2)
> >
> > Th
> -Original Message-
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Friday, October 04, 2013 10:43 PM
> To: Bhushan Bharat-R65777
> Cc: j...@8bytes.org; b...@kernel.crashing.org; ga...@kernel.crashing.org;
> linux-
> ker...@vger.kernel.org; linuxppc-dev@lists.ozlabs.
On Fri, 2013-10-04 at 16:47 +, Bhushan Bharat-R65777 wrote:
>
> > -Original Message-
> > From: Alex Williamson [mailto:alex.william...@redhat.com]
> > Sent: Friday, October 04, 2013 9:15 PM
> > To: Bhushan Bharat-R65777
> > Cc: j...@8bytes.org; b...@kernel.crashing.org; ga...@kernel.cr
> -Original Message-
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Friday, October 04, 2013 9:15 PM
> To: Bhushan Bharat-R65777
> Cc: j...@8bytes.org; b...@kernel.crashing.org; ga...@kernel.crashing.org;
> linux-
> ker...@vger.kernel.org; linuxppc-dev@lists.ozlabs.o
On Fri, 2013-10-04 at 22:24 +1000, Alexey Kardashevskiy wrote:
> This is a very rough change set required for ppc64 to use this KVM device.
>
> vfio_rm.c is a piece of code which is going to be called from the realmode
> (MMU off),
> and I will put everything spapr-related under #ifdef CONFIG_SPA
This more or less reverts commit 6391f697d4892a6f233501beea553e13f7745a23.
Instead of adding an unneeded 'default', mark the variable to prevent
the false positive 'uninitialized var'. The other change (fixing the
printout) needs revert, too. We want to know WHICH critical irq failed,
not which lev
On Fri, 2013-10-04 at 09:54 +, Bhushan Bharat-R65777 wrote:
>
> > -Original Message-
> > From: linux-pci-ow...@vger.kernel.org
> > [mailto:linux-pci-ow...@vger.kernel.org]
> > On Behalf Of Alex Williamson
> > Sent: Wednesday, September 25, 2013 10:16 PM
> > To: Bhushan Bharat-R65777
>
On 10/04/2013 05:37 PM, Wolfram Sang wrote:
> This more or less reverts commit 6391f697d4892a6f233501beea553e13f7745a23.
> Instead of adding an unneeded 'default', mark the variable to prevent
> the false positive 'uninitialized var'. The other change (fixing the
> printout) needs revert, too. We w
On 03.10.2013, at 09:58, Aneesh Kumar K.V wrote:
> From: "Aneesh Kumar K.V"
>
> This was introduced by 85a0d845d8 ("KVM: PPC: Book3S PR: Allocate
> kvm_vcpu structs from kvm_vcpu_cache").
>
> arch/powerpc/kvm/book3s_pr.c: In function 'kvmppc_core_vcpu_create':
> arch/powerpc/kvm/book3s_pr.c:11
On 10.07.2013, at 09:25, Michael Neuling wrote:
> Alexander Graf wrote:
>
>>
>> On 09.07.2013, at 06:24, Michael Neuling wrote:
>>
>>> Alexander Graf wrote:
>>>
On 04.07.2013, at 08:15, Bharat Bhushan wrote:
> From: Bharat Bhushan
>
> This patchset moves the d
Alexander Graf writes:
> On 04.10.2013, at 14:23, Alexander Graf wrote:
>
>>
>> On 03.10.2013, at 06:14, Paul Mackerras wrote:
>>
>>> On Wed, Oct 02, 2013 at 08:08:44PM +0530, Aneesh Kumar K.V wrote:
From: "Aneesh Kumar K.V"
This was introduced by 85a0d845d8bb5df5d2669416212f56
On 19.09.2013, at 08:02, Bharat Bhushan wrote:
> From: Bharat Bhushan
>
> First patch is a typo fix where book3e define _PAGE_LENDIAN while it
> should be defined as _PAGE_ENDIAN. This seems to show that this is never
> exercised :-)
>
> Second and third patch is to allow guest controlling "G
On 04.07.2013, at 08:57, Bharat Bhushan wrote:
> From: Bharat Bhushan
>
> Note: These patches depends on https://lkml.org/lkml/2013/7/4/49.
>
> This patchset adds the userspace debug support for booke/bookehv.
> this is tested on powerpc e500v2/e500mc devices.
Thanks, applied to kvm-ppc-queue
On 10/4/2013 3:03 PM, Thomas Hühn wrote:
Hi all,
We are several Openwrt users based on the TPlink 4900 device and suffer from a
crashing gianfar driver.
We troubleshooted the problem down to the fact, that a 3.8er Linux kernel is
working, and a v3.10 crashes, but there is
no reproducable case
> -Original Message-
> From: Alexander Graf [mailto:ag...@suse.de]
> Sent: Friday, October 04, 2013 6:57 PM
> To: Bhushan Bharat-R65777
> Cc: b...@kernel.crashing.org; pau...@samba.org; k...@vger.kernel.org; kvm-
> p...@vger.kernel.org; linuxppc-dev@lists.ozlabs.org; Wood Scott-B07421;
>
On 19.09.2013, at 08:02, Bharat Bhushan wrote:
> lookup_linux_pte() was searching for a pte and also sets access
> flags is writable. This function now searches only pte while
> access flag setting is done explicitly.
>
> This pte lookup is not kvm specific, so moved to common code (asm/pgtable.
On 04.10.2013, at 14:35, Paul Mackerras wrote:
> On Fri, Oct 04, 2013 at 02:27:02PM +0200, Alexander Graf wrote:
>>
>> On 04.10.2013, at 14:23, Alexander Graf wrote:
>>
>>>
>>> On 03.10.2013, at 06:14, Paul Mackerras wrote:
>>>
On Wed, Oct 02, 2013 at 08:08:44PM +0530, Aneesh Kumar K.V w
On Fri, Oct 04, 2013 at 02:27:02PM +0200, Alexander Graf wrote:
>
> On 04.10.2013, at 14:23, Alexander Graf wrote:
>
> >
> > On 03.10.2013, at 06:14, Paul Mackerras wrote:
> >
> >> On Wed, Oct 02, 2013 at 08:08:44PM +0530, Aneesh Kumar K.V wrote:
> >>> From: "Aneesh Kumar K.V"
> >>>
> >>> Thi
On 04.10.2013, at 14:23, Alexander Graf wrote:
>
> On 03.10.2013, at 06:14, Paul Mackerras wrote:
>
>> On Wed, Oct 02, 2013 at 08:08:44PM +0530, Aneesh Kumar K.V wrote:
>>> From: "Aneesh Kumar K.V"
>>>
>>> This was introduced by 85a0d845d8bb5df5d2669416212f56cbe1474c6b
>>
>> It's a good idea
This is a very rough change set required for ppc64 to use this KVM device.
vfio_rm.c is a piece of code which is going to be called from the realmode (MMU
off),
and I will put everything spapr-related under #ifdef CONFIG_SPAPR_TCE_IOMMU,
it is just friday and I have to run :)
This is an RFC but
On 03.10.2013, at 06:14, Paul Mackerras wrote:
> On Wed, Oct 02, 2013 at 08:08:44PM +0530, Aneesh Kumar K.V wrote:
>> From: "Aneesh Kumar K.V"
>>
>> This was introduced by 85a0d845d8bb5df5d2669416212f56cbe1474c6b
>
> It's a good idea to give the headline of the commit as well as the ID.
> I al
Hi Grant,
On 18/09/13 17:18, Sudeep KarkadaNagesha wrote:
> On 18/09/13 15:51, Grant Likely wrote:
>> On Wed, 18 Sep 2013 11:53:03 +0100, Sudeep KarkadaNagesha
>> wrote:
>>> From: Sudeep KarkadaNagesha
>>>
>>> Hi,
>>>
>>> The cache bindings are generic and used by many other architectures
>>> a
> -Original Message-
> From: Bhushan Bharat-R65777
> Sent: Friday, October 04, 2013 3:24 PM
> To: 'Alex Williamson'
> Cc: j...@8bytes.org; b...@kernel.crashing.org; ga...@kernel.crashing.org;
> linux-
> ker...@vger.kernel.org; linuxppc-dev@lists.ozlabs.org; linux-
> p...@vger.kernel.org;
> -Original Message-
> From: linux-pci-ow...@vger.kernel.org [mailto:linux-pci-ow...@vger.kernel.org]
> On Behalf Of Alex Williamson
> Sent: Wednesday, September 25, 2013 10:16 PM
> To: Bhushan Bharat-R65777
> Cc: j...@8bytes.org; b...@kernel.crashing.org; ga...@kernel.crashing.org;
> li
On Fri, Oct 04, 2013 at 09:31:49AM +0100, David Laight wrote:
> > Mmmm.. I am not sure I am getting it. Could you please rephrase?
>
> One possibility is for drivers than can use a lot of interrupts to
> request a minimum number initially and then request the additional
> ones much later on.
> Tha
> > It seems to me that a more useful interface would take a minimum and
> > maximum number of vectors from the driver. This wouldn't allow the
> > driver to specify that it could only accept, say, any even number within
> > a certain range, but you could still leave the current functions
> > avai
On Thu, Oct 03, 2013 at 11:49:45PM +0100, Ben Hutchings wrote:
> On Wed, 2013-10-02 at 12:48 +0200, Alexander Gordeev wrote:
> > This update converts pci_enable_msix() and pci_enable_msi_block()
> > interfaces to canonical kernel functions and makes them return a
> > error code in case of failure o
* Alexei Starovoitov wrote:
> on x86 system with net.core.bpf_jit_enable = 1
>
> sudo tcpdump -i eth1 'tcp port 22'
>
> causes the warning:
> [ 56.766097] Possible unsafe locking scenario:
> [ 56.766097]
> [ 56.780146]CPU0
> [ 56.786807]
> [ 56.793188] lock(&(&
On Wed, 2 Oct 2013 12:48:19 +0200
Alexander Gordeev wrote:
> Multiple MSIs have never been supported on s390 architecture,
> but the platform code fails to report single MSI only.
>
> Signed-off-by: Alexander Gordeev
> ---
> arch/s390/pci/pci.c |2 ++
> 1 files changed, 2 insertions(+), 0
On Wed, 2 Oct 2013 12:48:20 +0200
Alexander Gordeev wrote:
> arch_setup_msi_irqs() hook can only be called from the generic
> MSI code which ensures correct MSI type parameter.
>
> Signed-off-by: Alexander Gordeev
> ---
> arch/s390/pci/pci.c |2 --
> 1 files changed, 0 insertions(+), 2 de
60 matches
Mail list logo
