On Mon, Aug 29, 2016 at 02:30:46AM +0530, Madhavan Srinivasan wrote:
> It's a perennial request from hardware folks to be able to
> see the raw values of the pmu registers. Partly it's so that
> they can verify perf is doing what they want, and some
> of it is that they're interested in some of
From: Anshuman Khandual
For partition running on PHYP, there can be a adjunct partition
which shares the virtual address range with the operating system.
Virtual address ranges which can be used by the adjunct partition
are communicated with virtual device node of
On Wed, Aug 31, 2016 at 09:15:30AM -0700, Andi Kleen wrote:
> > >
> > > >
> > > > I've already made some changes in pmu-events/* to support
> > > > this hierarchy to see how bad the change would be.. and
> > > > it's not that bad ;-)
> > >
> > > Everything has to be automated, please no manual
> I didn't explain well, There is a CFE command 'show devtree' here's the
> relevant bits (I Hope)
This is much simple than I expected.
> [CFE ]CFE> show devtree
> [/]
> | #interrupt-cells val 0x0002
> | #address-cells val 0x0002
> | #size-cells
A bunch of KVM functions are only called from assembler.
Give them prototypes in asm-prototypes.h
Signed-off-by: Daniel Axtens
---
arch/powerpc/include/asm/asm-prototypes.h | 39 +++
arch/powerpc/kvm/book3s_64_vio_hv.c | 1 +
Another set of things that are only called from assembler and so need
prototypes to keep sparse happy.
Signed-off-by: Daniel Axtens
---
Again, created semi-programatically and compile-tested against
top-level defconfigs.
---
arch/powerpc/include/asm/asm-prototypes.h | 32
On 02/09/16 09:26, Daniel Axtens wrote:
Squash a bunch of sparse warnings by making things static.
Signed-off-by: Daniel Axtens
Reviewed-by: Andrew Donnellan
-struct irq_domain *iic_get_irq_host(int node)
+static struct irq_domain
Hi Daniel,
[auto build test WARNING on v4.8-rc4]
[also build test WARNING on next-20160825]
[cannot apply to powerpc/next kvm-ppc/kvm-ppc-next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or
Hi Daniel,
[auto build test ERROR on v4.8-rc4]
[also build test ERROR on next-20160825]
[cannot apply to powerpc/next kvm-ppc/kvm-ppc-next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or
On 9/1/16 11:46 PM, Thiago Jung Bauermann wrote:
Am Freitag, 26 August 2016, 11:50:10 schrieb Rui Teng:
The same logic appears twice and should probably be pulled out into a
function.
Suggested-by: Michael Ellerman
Signed-off-by: Rui Teng
---
Squash a bunch of sparse warnings by making things static.
Signed-off-by: Daniel Axtens
---
This is an omnibus patch - I wrote a Python script to figure out if
sparse warnings could be automatically fixed. These are the fixes
that didn't cause issues.
I have compile tested
This patch introduces the 'iommu_alloc_quiet=driver_name' parameter
to suppress the 'iommu_alloc failures' messages for that one driver.
This is an additional approach for this 'problem' of flooding logs,
not as fine-grained and not enabled by default as DMA_ATTR_NO_WARN,
but it has the advantage
Michael / Ben,
On 09/01/2016 09:56 AM, Mauricio Faria de Oliveira wrote:
+#define IOMMU_ALLOC_QUIET_LEN 16 /* includes '\0' */
Guilherme suggested MAX_PARAM_PREFIX_LEN for this, which looks
better (a few extra bytes).
Would you mind to s/16/MAX_PARAM_PREFIX_LEN/ if you like that?
I can send
On Thu, Sep 01, 2016 at 09:56:42AM -0300, Mauricio Faria de Oliveira wrote:
> This patch introduces the 'iommu_alloc_quiet=driver_name' parameter
> to suppress the 'iommu_alloc failures' messages for that one driver.
>
> This is an additional approach for this 'problem' of flooding logs,
> not as
On 09/01/2016 10:39 AM, Torsten Duwe wrote:
JFYI, my strongly preferred solution would still be to just dev_dbg() the whole
thing.
Which group of people would be interested in these messages, after all?
Certainly understandable.
Ben didn't like the idea to convert the messages to dynamic
Am Freitag, 26 August 2016, 11:50:10 schrieb Rui Teng:
> The same logic appears twice and should probably be pulled out into a
> function.
>
> Suggested-by: Michael Ellerman
> Signed-off-by: Rui Teng
> ---
> arch/powerpc/mm/hash_utils_64.c | 45
16 matches
Mail list logo