On 01/29/2016 10:54 AM, David Gibson wrote:
> +
> +static int pseries_lpar_resize_hpt_commit(void *data)
> +{
> + struct hpt_resize_state *state = data;
> +
> + state->commit_rc = plpar_resize_hpt_commit(0, state->shift);
> + if (state->commit_rc != H_SUCCESS)
> + return -E
On 01/29/2016 10:54 AM, David Gibson wrote:
> The hypervisor needs to know a guest is capable of using the HPT resizing
> PAPR extension in order to make full advantage of it for memory hotplug.
>
> If the hypervisor knows the guest is HPT resize aware, it can size the
> initial HPT based on the i
On 2016/1/30 3:01, Alex Williamson wrote:
On Fri, 2016-01-29 at 18:37 +0800, Yongji Xie wrote:
On 2016/1/29 6:46, Alex Williamson wrote:
On Fri, 2016-01-15 at 15:06 +0800, Yongji Xie wrote:
When vfio passthrough a PCI device of which MMIO BARs
are smaller than PAGE_SIZE, guest will not handle
On 01/29/2016 10:54 AM, David Gibson wrote:
> #ifdef CONFIG_MEMORY_HOTPLUG
> +void resize_hpt_for_hotplug(unsigned long new_mem_size)
> +{
> + unsigned target_hpt_shift;
> +
> + if (!ppc_md.resize_hpt)
> + return;
> +
> + target_hpt_shift = htab_shift_for_mem_size(new_mem_s
On 2016/1/30 3:05, Alex Williamson wrote:
- Original Message -
On 2016/1/29 6:46, Alex Williamson wrote:
On Fri, 2016-01-15 at 15:06 +0800, Yongji Xie wrote:
MSI-X tables are not allowed to be mmapped in vfio-pci
driver in case that user get to touch this directly.
This will cause som
On 01/02/16 17:03, Balbir Singh wrote:
From: Balbir Singh
I spent some time trying to use kgdb and debugged my inability to
resume from kgdb_handle_breakpoint(). NIP is not incremented
and that leads to a loop in the debugger.
I've tested this lightly on a virtual instance with KDB enabled.
Af
Replacing the NO_IRQ macro with 0. If there is no interrupt,
returned value will be 0 regardless of what NO_IRQ is defined.
Signed-off-by: Raghav Dogra
---
This patchset is dependent on the IFC deep sleep patch:
https://patchwork.ozlabs.org/patch/564785/
drivers/memory/fsl_ifc.c | 2 +-
1 file
IFC has two set of registers viz FCM (Flash control machine)
aka global and run time registers. These set are defined in two
memory map PAGES. Upto IFC 1.4 PAGE size is 4 KB and from IFC2.0
PAGE size is 64KB
Signed-off-by: Jaiprakash Singh
Signed-off-by: Raghav Dogra
---
drivers/memory/fsl_ifc.
On Mon, Feb 01, 2016 at 02:21:46PM +0530, Anshuman Khandual wrote:
> On 01/29/2016 10:54 AM, David Gibson wrote:
> > #ifdef CONFIG_MEMORY_HOTPLUG
> > +void resize_hpt_for_hotplug(unsigned long new_mem_size)
> > +{
> > + unsigned target_hpt_shift;
> > +
> > + if (!ppc_md.resize_hpt)
> > +
On Mon, Feb 01, 2016 at 02:01:09PM +0530, Anshuman Khandual wrote:
> On 01/29/2016 10:54 AM, David Gibson wrote:
>
> > +
> > +static int pseries_lpar_resize_hpt_commit(void *data)
> > +{
> > + struct hpt_resize_state *state = data;
> > +
> > + state->commit_rc = plpar_resize_hpt_commit(0, stat
IFC NAND is not working on ARM layescape platform due to
undefined macro FSL_SOC.
This patch fixes the dependency to enable NAND.
Signed-off-by: Raghav Dogra
---
drivers/memory/Kconfig | 2 +-
drivers/memory/fsl_ifc.c | 4 +++-
drivers/mtd/nand/Kconfig | 2 +-
3 files changed, 5 insertions(+),
lockup on fsl_ssi module reload,
> at least in AC'97 mode.
>
> Fixes: 05cf237972fe ("ASoC: fsl_ssi: Add driver suspend and resume to support
> MEGA Fast")
>
> Signed-off-by: Maciej S. Szmigiero
I know I have already tested this and it worked fine on a mx6sabresd,
b
;> support MEGA Fast")
>>
>> Signed-off-by: Maciej S. Szmigiero
>
> I know I have already tested this and it worked fine on a mx6sabresd,
> but running linux-next 20160201 on a mx6sl-evk the ssi driver does not
> probe anymore:
>
> [2.216954] fsl-asoc-ca
Hi Maciej,
On Mon, Feb 1, 2016 at 10:07 AM, Maciej S. Szmigiero
wrote:
> Is regmap patch from
> http://www.spinics.net/lists/kernel/msg2161934.html
> applied to the tested tree?
Yes, linux-next 20160201 contains this patch.
___
Linuxppc-de
On 01.02.2016 13:13, Fabio Estevam wrote:
> Hi Maciej,
>
> On Mon, Feb 1, 2016 at 10:07 AM, Maciej S. Szmigiero
> wrote:
>> Is regmap patch from
>> http://www.spinics.net/lists/kernel/msg2161934.html
>> applied to the tested tree?
>
> Yes, linux-next 201602
Hello Michael and Benjamin, any news on this one?
Quick correction in this email subject: it was cropped because it's too
long. The full title was "[PATCH 0/2] Two patches regarding EEH
availability checks - DLPAR/DDW crash avoidance"
___
Linuxppc-
On Thu, Jan 28, 2016 at 4:17 PM, Kees Cook wrote:
> Some callers of strtobool were passing a pointer to unterminated strings.
> This fixes the issue and consolidates some logic in cifs.
My comments below.
First of all I don't think currently there is an issue in cifs, since
strbool checks only f
tml
>>> applied to the tested tree?
>>
>> Yes, linux-next 20160201 contains this patch.
>
> Hmm, I will try to build this tree on UDOO board
> today and see what happens.
Looks like the problem occurs because commit
922a9f936e40 ("regmap: mmio: Convert to
From: Mahesh Salgaonkar
The kernel boot parameter 'nr_cpus=' allows one to specify number of
possible cpus in the system. In the normal scenario the first cpu (cpu0)
that shows up is the boot cpu and hence it gets covered under nr_cpus
limit.
But this assumption will be broken in kdump scenario
Hi Mahesh,
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.5-rc2 next-20160201]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Mahesh-J-Salgaonkar/ppc64-boot-Wait-for
Limit idle ticks to total ticks. This prevents the annoying rackmeter
leds fully ON / OFF blinking state that happens on fully idling
G5 Xserve systems.
Signed-off-by: Aaro Koskinen
---
drivers/macintosh/rack-meter.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/macintosh/rack-mete
Fix bogus memsets pointed out by sparse:
linux-v4.3/drivers/macintosh/rack-meter.c:157:15: warning: memset with byte
count of 0
linux-v4.3/drivers/macintosh/rack-meter.c:158:15: warning: memset with byte
count of 0
Probably "&" is mistyped "*"; use ARRAY_SIZE to make it more safe.
Signed-off-b
On Mon, Feb 1, 2016 at 4:46 AM, Raghav Dogra wrote:
A general comment is that you should include the linux-mtd mailing
list and it's maintainers for this set of patches. Although the
MAINTAINERS file doesn't specify a maintainer for drivers/memory
directory, it should be most related to linux-mt
Thanks!
Applied and it built this time, sadly i missed RC-2 and will just have to
test and see if the radeon r300 is un-broken and rebuild, doing dpkg kernel
build and was lazy with the .config so it takes a day building on this
single core g4!
Cheers
Mike
On 1 February 2016 at 01:05, Pranith Ku
On Mon, Feb 01, 2016 at 01:41:45PM -0600, Li Yang wrote:
> On Mon, Feb 1, 2016 at 4:46 AM, Raghav Dogra wrote:
>
> A general comment is that you should include the linux-mtd mailing
> list and it's maintainers for this set of patches. Although the
> MAINTAINERS file doesn't specify a maintainer
On Mon, Feb 01, 2016 at 05:58:06PM +0100, Maciej S. Szmigiero wrote:
> Looks like a possible solution would be to change
> regmap_raw_read() to do read using _regmap_read in
> case the cache is bypassed and there is no ->read
> callback defined for regmap implementation.
No, that's completely bro
On 01.02.2016 22:10, Mark Brown wrote:
> On Mon, Feb 01, 2016 at 05:58:06PM +0100, Maciej S. Szmigiero wrote:
>
>> Looks like a possible solution would be to change
>> regmap_raw_read() to do read using _regmap_read in
>> case the cache is bypassed and there is no ->read
>> callback defined for re
On Mon, Feb 1, 2016 at 7:30 PM, Maciej S. Szmigiero
wrote:
> So can regcache initialization be changed to use register by register read
> in case raw read fails?
>
> Since other option for drivers like SSI which are memory mapped and
> don't offer ability to reset their register values to default
On Mon, Feb 01, 2016 at 10:30:53PM +0100, Maciej S. Szmigiero wrote:
> On 01.02.2016 22:10, Mark Brown wrote:
> > No, that's completely broken. We can't do a raw read from a regmap that
> > doesn't offer raw access and we shouldn't pretend to do so. If the
> > caller is capable of substituting a
On Mon, 2016-02-01 at 16:16 +0530, Raghav Dogra wrote:
> /*
> * IFC Controller Registers
> */
> -struct fsl_ifc_regs {
> +struct fsl_ifc_fcm {
> __be32 ifc_rev;
> u32 res1[0x2];
> struct {
This struct is not specific to fcm (i.e. nand). Please choose a better name,
such as
On Mon, 1 Feb 2016 21:39:00 +1100
Andrew Donnellan wrote:
> On 01/02/16 17:03, Balbir Singh wrote:
> > From: Balbir Singh
> >
> > I spent some time trying to use kgdb and debugged my inability to
> > resume from kgdb_handle_breakpoint(). NIP is not incremented
> > and that leads to a loop in the
On Mon, Feb 01, 2016 at 11:20:03AM +0530, Anshuman Khandual wrote:
> On 01/29/2016 10:53 AM, David Gibson wrote:
> > Here's a second prototype of the guest side work for runtime resizing
> > of the has page table in PAPR guests.
> >
> > This is now feature complete. It implements the resizing, ad
On Mon, Feb 01, 2016 at 12:41:31PM +0530, Anshuman Khandual wrote:
> On 01/29/2016 10:54 AM, David Gibson wrote:
> > This adds the hypercall numbers and wrapper functions for the hash page
> > table resizing hypercalls.
> >
> > These are experimental "platform specific" values for now, until we ha
On Mon, Feb 01, 2016 at 12:34:32PM +0530, Anshuman Khandual wrote:
> On 01/29/2016 10:53 AM, David Gibson wrote:
> > htab_get_table_size() either retrieve the size of the hash page table (HPT)
> > from the device tree - if the HPT size is determined by firmware - or
> > uses a heuristic to determin
On Mon, Feb 01, 2016 at 11:28:54AM +0530, Anshuman Khandual wrote:
> On 01/29/2016 10:53 AM, David Gibson wrote:
> > At the moment the hpte_removebolted callback in ppc_md returns void and
> > will BUG_ON() if the hpte it's asked to remove doesn't exist in the first
> > place. This is awkward for
On Wed, Jan 13, 2016 at 05:10:31PM +1100, Russell Currey wrote:
>"p5ioc2 is used by approximately 2 machines in the world, and has never
>ever been a supported configuration."
>
>The code for p5ioc2 is essentially unused and complicates what is already
>a very complicated codebase. Its removal is
On 01/29/2016 02:45 PM, Anshuman Khandual wrote:
> On 01/28/2016 08:14 PM, Aneesh Kumar K.V wrote:
>> > Anshuman Khandual writes:
>> >
>>> >> This enables HugeTLB page migration for PPC64_BOOK3S systems which
>>> >> implement
>>> >> HugeTLB page at the PMD level. It enables the kernel configurat
Pranith Kumar writes:
> On Sun, Jan 31, 2016 at 8:01 PM, Mike wrote:
>> Building on ppc32
>>
>> In file included from fs/proc/task_mmu.c:14:0:
>> include/linux/swapops.h: In function ‘pte_to_swp_entry’:
>> include/linux/swapops.h:69:6: error: implicit declaration of function
>> ‘pte_swp_soft_dir
38 matches
Mail list logo
