Hi Ulf,
On Fri, Nov 23, 2012 at 04:54:09PM +0100, Ulf Hansson wrote:
> On 1 November 2012 15:20, Ulf Hansson wrote:
> > From: Ulf Hansson
> >
> > Due to the convert to the common clk driver these changes for clks are
> > needed.
> >
> > Ulf Hansson (2):
> > Input: nomadik-ske-keypad - fixup u
On Wed, Nov 14, 2012 at 01:47:17PM +, Lee Jones wrote:
> Here we add the required documentation for the STMPE Device
> Tree bindings. It describes all of the bindings currently
> supported by the driver.
Folded into the patch adding DT support to stmpe-keypad and applied.
Thank you Lee.
--
D
The default implementation matches exactly our custom one so we can switch
to using the default one. As a bonus the driver will take care of setting
GPIO line for us.
Signed-off-by: Dmitry Torokhov
---
Not tested - no hardware, but should be fine.
arch/arm/mach-imx/eukrea_mbimx27-baseboard.c |
On Mon, Nov 19, 2012 at 11:55:56AM -0800, Dmitry Torokhov wrote:
> On Fri, Nov 16, 2012 at 07:19:10PM -0500, Bill Pemberton wrote:
> > CONFIG_HOTPLUG is no longer an optional setting. In order to remove
> > it as on option code paths that check CONFIG_HOTPLUG will removed
> > along with the attrib
Original behavior:
bash-4.1$ make -C mqueue run_tests
make: Entering directory
`/home/dave/git/linux-2.6/tools/testing/selftests/mqueue'
./mq_open_tests /test1
Not running as root, but almost all tests require root in order to modify
system settings. Exiting.
make: *** [run_tests] Err
In case breakpoint test exit non zero value it will cause make error.
Better way is just print the test failure status.
Signed-off-by: Dave Young
---
tools/testing/selftests/breakpoints/Makefile |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-2.6.orig/tools/testing/selftests/
In case kcmp_test exit non zero value it will cause make error.
Better way is just print the test failure status.
Signed-off-by: Dave Young
---
tools/testing/selftests/kcmp/Makefile |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-2.6.orig/tools/testing/selftests/kcmp/Makefile
For old glibc there's no the syscall number this tests will cause
make run_tests fail.
Add a macro to define the number. This should be ok because it will be
built in latest kernel source.
Signed-off-by: Dave Young
---
tools/testing/selftests/kcmp/kcmp_test.c |3 +++
1 file changed, 3 insert
On Tue, Nov 13, 2012 at 10:38:28AM +0100, Peter Ujfalusi wrote:
> To facilitate upcoming cleanup in twl stack.
> No functional changes.
Applied, thank you Peter.
>
> Signed-off-by: Peter Ujfalusi
> ---
> drivers/input/misc/twl4030-pwrbutton.c | 3 +--
> 1 file changed, 1 insertion(+), 2 delet
bash-4.1$ make -C vm run_tests
make: Entering directory `/home/dave/git/linux-2.6/tools/testing/selftests/vm'
/bin/sh ./run_vmtests
./run_vmtests: line 24: /proc/sys/vm/nr_hugepages: Permission denied
Please run this test as root
make: *** [run_tests] Error 1
make: Leaving directory `
make run_tests need the target is run_tests instead of run-tests
Also gcc output should be kcmp_test. Fix these two issues.
Signed-off-by: Dave Young
---
tools/testing/selftests/kcmp/Makefile |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-2.6.orig/tools/testing/selftests
Hi, Andrew:
Here is several fixes for selftests.
For `make run_tests` the target command will cause make fail if it exit
with non zero codes. So I change the makefile as below:
run_tests: all
- /bin/sh ./run_vmtests
+ @/bin/sh ./run_vmtests || echo "vmtests: [FAIL]"
Also fixed the kc
bash-4.1$ make -C memory-hotplug run_tests
make: Entering directory
`/home/dave/git/linux-2.6/tools/testing/selftests/memory-hotplug'
./on-off-test.sh
make: execvp: ./on-off-test.sh: Permission denied
make: *** [run_tests] Error 127
make: Leaving directory
`/home/dave/git/linux-2.6/to
bash-4.1$ make -C cpu-hotplug run_tests
make: Entering directory
`/home/dave/git/linux-2.6/tools/testing/selftests/cpu-hotplug'
./on-off-test.sh
make: execvp: ./on-off-test.sh: Permission denied
make: *** [run_tests] Error 127
make: Leaving directory
`/home/dave/git/linux-2.6/tools/te
On Saturday 24 November 2012 01:26:42 Cesar Eduardo Barros wrote:
> This driver was removed by commit 6187fee (mmc: remove imxmmc driver).
>
> Cc: Sascha Hauer
> Cc: Pavel Pisa
> Cc: linux-arm-ker...@lists.infradead.org
> Signed-off-by: Cesar Eduardo Barros
> ---
> MAINTAINERS | 6 --
> 1 f
Hi Cesar,
On Fri, 23 Nov 2012 22:26:37 -0200, Cesar Eduardo Barros wrote:
> This file was moved to drivers/i2c/i2c-stub.c by commit 31d178b
> (i2c-stub: Move to drivers/i2c).
>
> Cc: Jean Delvare
> Cc: "Mark M. Hoffman"
> Cc: linux-...@vger.kernel.org
> Signed-off-by: Cesar Eduardo Barros
> --
Il 18/11/2012 09:59, Marco Stornelli ha scritto:
Il 20/10/2012 12:02, Marco Stornelli ha scritto:
With the commit 3be2be0a32c18b0fd6d623cda63174a332ca0de1 we removed
vmtruncate,
but actaully there is no need to call inode_newsize_ok() because the
checks are
already done in inode_change_ok() at t
Am Sat, 24 Nov 2012 10:02:32 +0100
schrieb Marco Stornelli :
> Il 18/11/2012 09:59, Marco Stornelli ha scritto:
> > Il 20/10/2012 12:02, Marco Stornelli ha scritto:
> >> With the commit 3be2be0a32c18b0fd6d623cda63174a332ca0de1 we removed
> >> vmtruncate,
> >> but actaully there is no need to call
Il 24/11/2012 10:12, Richard Weinberger ha scritto:
Am Sat, 24 Nov 2012 10:02:32 +0100
schrieb Marco Stornelli :
Il 18/11/2012 09:59, Marco Stornelli ha scritto:
Il 20/10/2012 12:02, Marco Stornelli ha scritto:
With the commit 3be2be0a32c18b0fd6d623cda63174a332ca0de1 we removed
vmtruncate,
bu
After my system got stuck with 3.7.0-rc2 as reported in
http://marc.info/?l=linux-kernel&m=135142236520624 LOCKDEP seem to
blame XFS, because it found 2 possible deadlocks. But after these
locking issues where fixed, my system got stuck again with 3.7.0-rc6
as reported in http://marc.info/?l=linux-
From: Rafael J. Wysocki
Local variable 'error' in dev_pm_qos_add_ancestor_request() need
not contain error codes only, so rename it to 'ret'.
Signed-off-by: Rafael J. Wysocki
---
drivers/base/power/qos.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
Index: linux/drivers/b
On Sat, Nov 24, 2012 at 10:29 AM, wrote:
> For old glibc there's no the syscall number this tests will cause
> make run_tests fail.
> Add a macro to define the number. This should be ok because it will be
> built in latest kernel source.
>
> Signed-off-by: Dave Young
> ---
> tools/testing/selft
On Sat, Nov 24, 2012 at 10:29 AM, wrote:
> bash-4.1$ make -C memory-hotplug run_tests
> make: Entering directory
> `/home/dave/git/linux-2.6/tools/testing/selftests/memory-hotplug'
> ./on-off-test.sh
> make: execvp: ./on-off-test.sh: Permission denied
> make: *** [run_tests] Error 127
On Sat, Nov 24, 2012 at 10:29 AM, wrote:
> bash-4.1$ make -C cpu-hotplug run_tests
> make: Entering directory
> `/home/dave/git/linux-2.6/tools/testing/selftests/cpu-hotplug'
> ./on-off-test.sh
> make: execvp: ./on-off-test.sh: Permission denied
> make: *** [run_tests] Error 127
> ma
On Sat, Nov 24, 2012 at 10:29 AM, wrote:
> Original behavior:
> bash-4.1$ make -C mqueue run_tests
> make: Entering directory
> `/home/dave/git/linux-2.6/tools/testing/selftests/mqueue'
> ./mq_open_tests /test1
> Not running as root, but almost all tests require root in order to modify
>
On Sat, Nov 24, 2012 at 10:29 AM, wrote:
> In case kcmp_test exit non zero value it will cause make error.
> Better way is just print the test failure status.
>
> Signed-off-by: Dave Young
Reviewed-by: Pekka Enberg
> ---
> tools/testing/selftests/kcmp/Makefile |2 +-
> 1 file changed, 1
On Sat, Nov 24, 2012 at 10:29 AM, wrote:
> In case breakpoint test exit non zero value it will cause make error.
> Better way is just print the test failure status.
>
> Signed-off-by: Dave Young
Reviewed-by: Pekka Enberg
> ---
> tools/testing/selftests/breakpoints/Makefile |2 +-
> 1 fil
On 2012.11.23 at 14:23 +0100, Takashi Iwai wrote:
> Sound fixes for 3.7-rc7
>
> The highlight of this update is the fixes for ASoC kirkwood by Russell.
> In addition to that, a couple of regression fixes for HD-audio due to
> the runtime PM support on 3.7, and other driver-specific regression
> fi
On Monday, November 12, 2012 10:00:07 PM Arnd Bergmann wrote:
> On Wednesday 07 November 2012, Rob Herring wrote:
> > From: Rob Herring
> >
> > Add support for core powergating on Calxeda platforms. Initially, this
> > supports ECX-1000 (highbank), but support will be added for ECX-2000
> > later
On Saturday, November 17, 2012 03:50:48 PM Borislav Petkov wrote:
> On Tue, Nov 13, 2012 at 02:13:38PM -0500, Mark Langsdorf wrote:
> > Although cpufreq_driver has a flag field, no part of cpufreq_driver
> > is directly passed to the cpufreq_stat code. Only cpufreq_policy
> > is. It's cleaner to do
Hi Mark,
On Wednesday, November 07, 2012 12:32:40 PM Mark Langsdorf wrote:
> This patch series adds cpufreq support for the Calxeda
> ECX-1000 (highbank) SoCs. The driver is based on the
> cpufreq-cpu0 driver. Because of the unique way that
> highbank uses the EnergyCore Management Engine to man
On 11/23/2012 03:13 PM, Thierry Reding wrote:
> Add support for reading conversion results from the ADC and provide them
> through a single IIO channel. A proper scaling factor is also exported
> based on the reference voltage provided by a regulator.
>
> Signed-off-by: Thierry Reding
Looks good
At Sat, 24 Nov 2012 10:46:10 +0100,
Markus Trippelsdorf wrote:
>
> On 2012.11.23 at 14:23 +0100, Takashi Iwai wrote:
> > Sound fixes for 3.7-rc7
> >
> > The highlight of this update is the fixes for ASoC kirkwood by Russell.
> > In addition to that, a couple of regression fixes for HD-audio due t
On 24 November 2012 12:33, Alessandro Rubini wrote:
> My patch:
>>> This driver would not compile if ARM_AMBA is selected under x86,
>>> because "CS" and "DS" are already defined there. But AMBA
>>> is used in the x86 world by a PCI-to-AMBA bridge, to be submitted.
>>>
>>> The patch just adds the
use devm_kzalloc and remove the error path free'ing and unload free'ing
as the devm resource functions free them.
Signed-off-by: Devendra Naga
---
drivers/mfd/jz4740-adc.c | 23 +++
1 file changed, 7 insertions(+), 16 deletions(-)
diff --git a/drivers/mfd/jz4740-adc.c b/driv
Ian Kent writes:
> On Sat, 2012-11-24 at 10:23 +0800, Ian Kent wrote:
>> On Fri, 2012-11-23 at 15:30 +0100, Miklos Szeredi wrote:
>> > Ian Kent writes:
>> >
>> > > On Fri, 2012-11-23 at 11:45 +0800, Ian Kent wrote:
>> > >> On Thu, 2012-11-22 at 17:24 +0100, Miklos Szeredi wrote:
>> > >> > Patch
Building ewrk3.o triggers this GCC warning:
drivers/net/ethernet/dec/ewrk3.c: In function '__check_irq':
drivers/net/ethernet/dec/ewrk3.c:1915:1: warning: return from incompatible
pointer type [enabled by default]
This can be trivially fixed by changing the 'irq' parameter from int to
byt
"H. Peter Anvin" writes:
> On 11/22/2012 10:28 AM, Yinghai Lu wrote:
>>
>> has problem with old kexec, it only copy header from bzImage include
>> setup_header as boot_param.
>>
>
> How old are we talking here? This is a clear and blatant bug, and it would
> affect a whole bunch of things, not ju
Hi Oleg,
> Amnon,
>
> I am going to "ignore" this thread because this is not my area and
> I can't help anyway. Just one note:
>
> On 11/23, Amnon Shiloh wrote:
> >
> > The solution can be to hold all catched signals while in the VDSO page.
> > ...
> >
> > 1) + introduce a kernel feature to prev
Hi,
This patchset try to solve one deadlock problem which might be caused
by memory allocation with block I/O during runtime PM and block device
error handling path. Traditionly, the problem is addressed by passing
GFP_NOIO statically to mm, but that is not a effective solution, see
detailed descr
This patch introduces PF_MEMALLOC_NOIO on process flag('flags' field of
'struct task_struct'), so that the flag can be set by one task
to avoid doing I/O inside memory allocation in the task's context.
The patch trys to solve one deadlock problem caused by block device,
and the problem may happen
The patch introduces the flag of memalloc_noio in 'struct dev_pm_info'
to help PM core to teach mm not allocating memory with GFP_KERNEL
flag for avoiding probable deadlock.
As explained in the comment, any GFP_KERNEL allocation inside
runtime_resume() or runtime_suspend() on any one of device in
This patch applyes the introduced pm_runtime_set_memalloc_noio on
block device so that PM core will teach mm to not allocate memory with
GFP_IOFS when calling the runtime_resume and runtime_suspend callback
for block devices and its ancestors.
Cc: Jens Axboe
Signed-off-by: Ming Lei
---
v5:
Deadlock might be caused by allocating memory with GFP_KERNEL in
runtime_resume and runtime_suspend callback of network devices in
iSCSI situation, so mark network devices and its ancestor as
'memalloc_noio' with the introduced pm_runtime_set_memalloc_noio().
Cc: "David S. Miller"
Cc: Eric Dumaze
This patch applies the introduced memalloc_noio_save() and
memalloc_noio_restore() to force memory allocation with no I/O
during runtime_resume/runtime_suspend callback on device with
the flag of 'memalloc_noio' set.
Cc: Alan Stern
Cc: Oliver Neukum
Cc: Rafael J. Wysocki
Signed-off-by: Ming Lei
If one storage interface or usb network interface(iSCSI case)
exists in current configuration, memory allocation with
GFP_KERNEL during usb_device_reset() might trigger I/O transfer
on the storage interface itself and cause deadlock because
the 'us->dev_mutex' is held in .pre_reset() and the storag
On Sat, Nov 24, 2012 at 12:17:03PM +0800, Hillf Danton wrote:
> A thp contributes 512 times more than a regular page to numa fault stats,
> so deserves its own vm event counter. THP migration is also accounted.
>
I agree and mentioned it needed fixing. I did not create a new counter
but I properl
On Sat, Nov 24, 2012 at 12:18:51PM +0800, Hillf Danton wrote:
> Free newly allocated thp if fail to isolate the old.
>
> Signed-off-by: Hillf Danton
Thanks!
--
Mel Gorman
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@
On Sat, Nov 24, 2012 at 12:27:39PM +0800, Hillf Danton wrote:
> If fail to migrate thp(due to unsuccessful isolation), and if the original
> pmd entry is changed after reaquiring page table lock, it is unsafe to
> release the page lock as page maybe unstable.
>
> It is fixed by raising extra page
Hi Oleg,
> Hello Amnon,
>
> I am a bit confused,
So let's get things in order.
1) I asked for the ability to set hardware breakpoints on the vsyscall
page (x86 debug registers), so that the ptracer can stop the process
whenever it attempts to jump there, then the ptracer can emulate those
Linus,
The following changes since commit 947d299686aa9cc8aecf749d54e8475c6e498956:
ALSA: snd-usb: properly initialize the sync endpoint (2012-11-22 21:22:33
+0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git tags/sound-3.7
for you
Hi Oleg,
This patch may look ugly, but it is one way to solve my problem.
This way, "strace" too, which is broken since the introduction of
the vsyscall page, will again be able to report when the program
calls "time()" or "gettimeofday()" - currently it cannot!
I think that allowing to set the
On Sat, Nov 24, 2012 at 08:02:40AM +0100, Thomas Petazzoni wrote:
> Dear Jason Cooper,
>
> On Fri, 23 Nov 2012 21:39:42 -0500, Jason Cooper wrote:
> > > + pinctrl: pinctrl@d0200 {
> > > + compatible = "marvell,dove-pinctrl";
> > > + reg = <0xd0200 0x10>;
> >
Acked-by: Javier Muñoz
Thanks Cesar!
Javier
On 11/24/2012 01:26 AM, Cesar Eduardo Barros wrote:
> This directory was moved to drivers/staging/sm7xxfb/ by commit 925aa66
> (staging: sm7xxfb: sm7xx becomes sm7xxfb).
>
> Cc: Teddy Wang
> Cc: Javier M. Mellid
> Signed-off-by: Cesar Eduardo Barro
On Thu, Nov 22, 2012 at 5:41 PM, Fengguang Wu wrote:
> On Wed, Nov 21, 2012 at 12:07:22PM +0200, Metin Döşlü wrote:
>> On Wed, Nov 21, 2012 at 12:00 PM, Jaegeuk Hanse
>> wrote:
>> >
>> > On 11/21/2012 05:58 PM, metin d wrote:
>> >
>> > Hi Fengguang,
>> >
>> > I run tests and attached the results
On Wed, Nov 21, 2012 at 12:10:43AM +, Alan Cox wrote:
> > Not just a separate document but project / github / whatever given
> > that other projects are referring to it now, and we stand to gain more
> > in the community by streamlining it more and making it ubiquitous.
>
> Cutting and pasting
On 11/24/2012 11:54 AM, Jonathan Cameron wrote:
> On 11/23/2012 03:13 PM, Thierry Reding wrote:
>> Add support for reading conversion results from the ADC and provide them
>> through a single IIO channel. A proper scaling factor is also exported
>> based on the reference voltage provided by a regul
On 11/23, Oleg Nesterov wrote:
>
> Change install_breakpoint() to call filter_chain() instead of checking
> uprobe->consumers != NULL. We obviously need this, and this equally
> closes the race with _unregister().
>
> Change remove_breakpoint() to call this helper too. Currently this is
> pointless
On 11/24/2012 03:54 PM, Lars-Peter Clausen wrote:
> On 11/24/2012 11:54 AM, Jonathan Cameron wrote:
>> On 11/23/2012 03:13 PM, Thierry Reding wrote:
>>> Add support for reading conversion results from the ADC and provide them
>>> through a single IIO channel. A proper scaling factor is also exporte
At 2012/11/24 1:50, Vasilis Liaskovitis Wrote:
> Consider the following sequence of operations for a hotplugged memory device:
>
> 1. echo "PNP0C80:XX"> /sys/bus/acpi/drivers/acpi_memhotplug/unbind
> 2. echo "PNP0C80:XX"> /sys/bus/acpi/drivers/acpi_memhotplug/bind
> 3. echo 1>/sys/bus/pci/device
At 2012/11/24 1:50, Vasilis Liaskovitis Wrote:
> Offlining and removal of memory is now done in the prepare_remove callback,
> not in the remove callback.
>
> The prepare_remove callback will be called when trying to remove a memory
> device
> with the following ways:
>
> 1. send eject request b
From: "Anthony G. Basile"
stime and utime are declared __u64 but are never used. On a glibc system
this is harmless lint, but on a uClibc system, because of the difference
in they way header files stack, including stdio.h brings in time.h and
this causes a name collision with stime. Since these
This patch introduce the use of the sysfs attribute for the spidev
configuration. This avoid the user to have a specific program which does
ioctl() on spidev. The user can easily does cat (to read) and echo (to
write) on the sysfs file and configure SPI.
The patch exports the following attributes:
On 11/24/2012 04:37 AM, Eric W. Biederman wrote:
Certainly /sbin/kexec isn't bothering to calculate the end of the setup
header and just being far more conservative and using all of the 16bit
real mode code as it's initializer.
That's not conservative... that's just plain wrong. It means you
On 11/21/2012 12:50 AM, Linus Walleij wrote:
> To be crystal clear on what the arguments mean in this
> funtion dealing with both GPIO and PIN ranges with confusing
> naming, we now have gpio_offset and pin_offset and we are
> on the clear that these are offsets into the specific GPIO
> and pin con
On Fri, Nov 23, 2012 at 11:47:16PM +0800, Axel Lin wrote:
> This driver can be built as a module, add MODULE_ALIAS for it.
Applied, thanks.
signature.asc
Description: Digital signature
On Fri, Nov 23, 2012 at 10:27:12AM +0800, Qing Xu wrote:
> But, in fact, it is not necessary to initialize regulator_idx.
> for (i = 0; i < ARRAY_SIZE(max8925_regulator_info); i++) {
> ri = &max8925_regulator_info[i];
> if (ri->vol_reg == res->start) {
> *
On Fri, Nov 23, 2012 at 01:33:13PM +0530, Thomas Abraham wrote:
> The BUCKxDVSx register programming is now moved prior to setting up of the
> gpio based dvs mode. This will ensure that all the BUCKxDVSx registers
> are programmed with appropriate voltage values before the gpio based dvs
> mode is
On Fri, Nov 23, 2012 at 01:33:14PM +0530, Thomas Abraham wrote:
> In case the gpio based volatage selection mode is not used for either of
> buck 1/2/5, then only the BUCKxDVS1 register need to be programmed. So
> determine whether dvs mode is used and limit the loop count appropriately.
Applied,
On Fri, Nov 23, 2012 at 01:33:15PM +0530, Thomas Abraham wrote:
> This v6 patch is rebased to the latest max8997 driver code and there are no
> functional changes from v5.
That doesn't seem to be in mainline yet so the patch won't apply.
signature.asc
Description: Digital signature
Hello.
On top of
"[PATCH 0/7] uprobes: register/unregister preparations for filtering"
4/4 is not really needed and I won't insist if you dislike it.
Just this ->copy_mutex annoys me ;)
Please review. filter_chain() is almost ready, just we need to
discuss (again) its arguments/etc and reintrodu
Introduce uprobe->register_rwsem. It is taken for writing around
__uprobe_register/unregister.
Change handler_chain() to use this sem rather than consumer_rwsem.
The main reason for this change is that we have the nasty problem
with mmap_sem/consumer_rwsem dependency. filter_chain() needs to
prot
Simply remove UPROBE_RUN_HANDLER and the corresponding code.
It can only help if uprobe has a single consumer, and in fact
it is no longer needed after handler_chain() was changed to use
->register_rwsem, we simply can not race with uprobe_register().
Signed-off-by: Oleg Nesterov
---
kernel/eve
Now that ->register_rwsem is safe under ->mmap_sem we can kill
->copy_mutex and abuse down_write(&uprobe->consumer_rwsem).
This makes prepare_uprobe() even more ugly, but we should kill
it anyway.
Signed-off-by: Oleg Nesterov
---
kernel/events/uprobes.c |7 +++
1 files changed, 3 insert
Now that it safe to use ->consumer_rwsem under ->mmap_sem we can
almost finish the implementation of filter_chain(). It still lacks
the actual uc->filter(...) call but othewrwise it is ready, just
it pretends that ->filter() always returns true.
Signed-off-by: Oleg Nesterov
---
kernel/events/upr
Dear Jason Cooper,
On Sat, 24 Nov 2012 10:00:04 -0500, Jason Cooper wrote:
> Yes, so that's what I thought happened. This would have made orion/dt
> depend upon mvebu/everything. It already had two other dependencies.
> Not ideal.
>
> The good thing is, the build is not broken. Once v3.8-rc1
On 24 November 2012 23:29, Mark Brown
wrote:
> On Fri, Nov 23, 2012 at 01:33:15PM +0530, Thomas Abraham wrote:
>
>> This v6 patch is rebased to the latest max8997 driver code and there are no
>> functional changes from v5.
>
> That doesn't seem to be in mainline yet so the patch won't apply.
Hi M
On 11/24/2012 10:12 AM, Yinghai Lu wrote:
Now I have a fix ready, also found fix for kexec real mode path working
with recently kernel by settin heap end ptr correctly.
Please decide if we need to add 64 bit entry offset in setup header,
Or just stick to 0x200.
I check grub2 and gujin and qemu
On Fri, Nov 23, 2012 at 10:26:44PM -0200, Cesar Eduardo Barros wrote:
> Added by commit 200efed (pwm: Take over maintainership of the PWM
> subsystem), but I could not find any trace of that file being ever added
> to the repository.
>
> Cc: Thierry Reding
> Signed-off-by: Cesar Eduardo Barros
>
On Sat, Nov 24, 2012 at 07:10:24PM +0100, Thomas Petazzoni wrote:
> Dear Jason Cooper,
>
> On Sat, 24 Nov 2012 10:00:04 -0500, Jason Cooper wrote:
>
> > Yes, so that's what I thought happened. This would have made orion/dt
> > depend upon mvebu/everything. It already had two other dependencies.
Any ideas on that? I'm currently avoiding the 3.6 series because
of that problem but would be willing to reproduce the hang if I'd
know what to do once it happens, ie. what kind of information to
collect in order to identify the cause of the problem.
I may also try 3.7-rc if there's any interest.
Hi,
Is the following normal on an X9SRL-F board (bios 1.0a)?
In the manual it states:
Data Direct I/O
Select Enabled to enable Intel I/OAT (I/O Acceleration Technology), which
significantly reduces CPU overhead by leveraging CPU architectural
improvements and freeing the system resource for othe
On 11/24/2012 09:32 AM, H. Peter Anvin wrote:
On 11/24/2012 04:37 AM, Eric W. Biederman wrote:
Certainly /sbin/kexec isn't bothering to calculate the end of the setup
header and just being far more conservative and using all of the 16bit
real mode code as it's initializer.
That's not conserv
On Fri, 2012-11-23 at 22:26 -0200, Cesar Eduardo Barros wrote:
> These files were renamed by commit 85fd6d6 (ARM: S3C2410: move
> mach-s3c2410/* into mach-s3c24xx/).
I submitted an identical patch in https://lkml.org/lkml/2012/6/25/154 .
In a reaction on that patch Kukjin Kim wondered whether "Sim
On Sat, 2012-11-24 at 21:28 +0100, Paul Bolle wrote:
> I submitted an identical patch in https://lkml.org/lkml/2012/6/25/154 .
> In a reaction on that patch Kukjin Kim wondered whether "Simtec Linux
> Team and Vincent are still supporting BAST". No-one bothered to reply on
> Kukjin's message, which
On Fri, Nov 23, 2012 at 01:48:51PM +0100, Peter Korsgaard wrote:
> > "Thierry" == Thierry Reding writes:
>
> Hi,
>
> Thierry> Everybody seems to be doing it with a warning, so I guess
> Thierry> that's fine for now. I just find it strange that if you
> Thierry> request the default pin gro
Now we have limit kdump reseved under 896M, because kexec has the limitation.
and also bzImage need to stay under 4g.
To make kexec/kdump could use range above 4g, we need to make bzImage and
ramdisk could be loaded above 4g.
During booting bzImage will be unpacked on same postion and stay high.
commit 08da5a2ca
x86_64: Early segment setup for VT
add lldt/ltr to clean more segments.
Those code are put in code64, and it is using gdt that is only
loaded from code32 path.
That breaks booting with 64bit bootloader that does not go through
code32 path. It get at startup_64 directly, an
Current when kernel is loaded above 1G, only [_text, _text+2M] is set
up with extra ident page table.
That is not enough, some variables that could be used early are out of
that range, like BRK for early page table.
Need to set map for [_text, _end] include text/data/bss/brk...
Also current kernel
ext_ramdisk_image/size will record high 32bits for ramdisk info.
xloadflags bit0 will be set if relocatable with 64bit.
Let get_ramdisk_image/size to use ext_ramdisk_image/size to get
right positon for ramdisk.
bootloader will fill value to ext_ramdisk_image/size when it load
ramdisk above 4G.
cmdline.c::__cmdline_find_option... are shared between
16-bit setup code and 32/64 bit decompressor code.
for 32/64 only path via kexec, we should not check if ptr less 1M.
as those cmdline could be put above 1M, or even 4G.
Move out accessible checking out of __cmdline_find_option()
So decompres
They are the same, could move them out from head32/64.c to setup.c.
We are using memblock, and it could handle overlapping properly, so
we don't need to reserve some at first to hold the location, and just
need to make sure we reserve them before we are using memblock to find
free mem to use.
Sig
We are short of space before 0x200 that is entry for startup_64.
According to hpa, we can not change startup_64 to other offset and
that become ABI now.
We could move function verify_cpu down, and that could avoid extra
code of jmp back and forth if we would move other lines.
Signed-off-by: Ying
boot/compressed/misc.c could be with 64 bit, and cmd_line_ptr could
above 4g.
So change to unsigned long instead, that will be 64bit in 64bit path
and 32bit in 32bit path.
Signed-off-by: Yinghai Lu
---
arch/x86/boot/boot.h|8
arch/x86/boot/cmdline.c |4 ++--
2 files changed
Now 64bit kernel supports more than 1T ram and kexec tools
could find buffer above 1T, remove that obsolete limitation.
and use MAXMEM instead.
Tested on system more than 1024G ram.
Signed-off-by: Yinghai Lu
Cc: "Eric W. Biederman"
---
arch/x86/include/asm/kexec.h |6 +++---
1 files change
There several places to find ramdisk information early for reserving
and relocating.
Use functions to make code more readable and consistent.
Later will add ext_ramdisk_image/size in those functions to support
loading ramdisk above 4g.
Signed-off-by: Yinghai Lu
---
arch/x86/kernel/setup.c |
later will check ext_cmd_line_ptr at the same time.
Signed-off-by: Yinghai Lu
---
arch/x86/boot/compressed/cmdline.c | 10 --
arch/x86/kernel/head64.c | 13 +++--
2 files changed, 19 insertions(+), 4 deletions(-)
diff --git a/arch/x86/boot/compressed/cmdline.c
b/a
When 64bit bootloader put real mode data above 4g, We can not
access real mode data directly yet.
because in arch/x86/kernel/head_64.S, only set ident mapping
for 0-1g, and kernel code/data/bss.
So need to move early_ioremap_init() calling early from setup_arch()
to x86_64_start_kernel().
Also u
On Sat, Nov 24, 2012 at 10:54:03AM +, Jonathan Cameron wrote:
> On 11/23/2012 03:13 PM, Thierry Reding wrote:
> > Add support for reading conversion results from the ADC and provide them
> > through a single IIO channel. A proper scaling factor is also exported
> > based on the reference voltag
On Sat, 24 Nov 2012, Jeff Chua wrote:
> On Fri, Nov 23, 2012 at 9:24 PM, Jens Axboe wrote:
> > On 2012-11-22 20:21, Linus Torvalds wrote:
> >> Doesn't sound like a fsdevel issue since it seems to be independent of
> >> filesystems. More like some generic block layer thing. Adding Jens
> >> (and
1 - 100 of 134 matches
Mail list logo
