Based on the recent discussion about 64-bit time_t for new
architectures, and for solving the year 2038 problem in general,
I decided to try out what it would take to solve part of the
kernel side of things.
This is a proof-of-concept work to get us to the point where
two system calls (utimes and
This adds the newly added system calls for newfstat64, newfstatat64
and utimens64at to x86, arm and all architectures using the generic
syscall ABI.
Signed-off-by: Arnd Bergmann
---
arch/arm/include/asm/unistd.h | 2 +-
arch/arm/include/uapi/asm/stat.h | 25 +
arc
We want to be able to read file system timestamps beyond year 2038,
which is currently impossibly on 32-bit systems, since none of the
various stat syscall interfaces (oldstat, stat, stat64) handles
correctly.
This introduces a fourth version of the syscalls, called newfstat64
and newfstatat64, wh
afs uses an unsigned 32-bit seconds numbers for inode timestamps on the
wire, which will work for the next 92 years, but the code internally
uses a signed time_t, which is only good until 2038 on 32-bit CPUs.
This gets us one small step closer to lifting the VFS limit by using
struct inode_time in
This converts the coda file system to use inode_time, which we will
need to fix the y2038 limit. However, inode time stamps in coda
are communicated to user space through coda_pioctl() as a 'struct
timespec', so this cannot be fixed for coda without changing the
user space interface.
Signed-off-by
xfs uses unsigned 32-bit seconds for inode timestamps, which will work
for the next 92 years, but the VFS uses struct timespec for timestamps,
which is only good until 2038 on 32-bit CPUs.
This gets us one small step closer to lifting the VFS limit by using
struct inode_time in XFS.
Signed-off-by
On 05/30/2014 01:00 PM, Andy Lutomirski wrote:
>
> Do the flags go in the ELF loader or in the executable we're running?
> Or both (and, if both, do we and them or or them)?
>
> I think the interpreter makes a little more sense in general: for the
> most part, use of vsyscalls is a property of th
Ceph supports timestamps until year 2106 using u32 seconds on the
wire, but the kernel internally limits this to a signed value
that only works until 2038 on 32 bit CPUs.
This changes the type used in the ceph code to struct inode_time
to lift that limitation.
Signed-off-by: Arnd Bergmann
Cc: Sa
cifs uses multiple time formats for inode timestamps, which will work
at least another 92 years, but the VFS uses struct timespec for timestamps,
which is only good until 2038 on 32-bit CPUs.
This gets us one small step closer to lifting the VFS limit by using
struct inode_time in cifs. After 2106
udf uses 16-bit year numbers for inode timestamps, which will work
for the 15000 years, but the VFS uses struct timespec for timestamps,
and the Linux udf implementation internally uses a time_t, both of
which are only good until 2038 on 32-bit CPUs.
This gets us one small step closer to lifting t
On 30 May 2014 08:29, Peter Zijlstra wrote:
> On Thu, May 29, 2014 at 09:37:39PM +0200, Vincent Guittot wrote:
>> On 29 May 2014 11:50, Peter Zijlstra wrote:
>> > On Fri, May 23, 2014 at 05:53:04PM +0200, Vincent Guittot wrote:
>> >> If the CPU is used for handling lot of IRQs, trig a load balanc
On 05/30/2014 08:48 AM, Andy Lutomirski wrote:
> This adds a macro GET(x) to convert x from big-endian to
> little-endian. Hopefully I put it everywhere it needs to go and got
> all the cases needed for everyone's linux/elf.h.
>
> Signed-off-by: Andy Lutomirski
> ---
> arch/x86/vdso/vdso2c.c |
On Wed, May 28, 2014 at 2:45 PM, H. Peter Anvin wrote:
> On 05/23/2014 09:40 AM, Andy Lutomirski wrote:
>>
>> I don't think this should be something configured by the
>> administrator, unless the administrator is the builder of a kiosky
>> thing like Chromium OS. In that case, the administrator c
On Thu, May 29, 2014 at 03:33:57PM +0200, Sebastian Reichel wrote:
> On Wed, May 21, 2014 at 07:36:10PM +0200, Sebastian Reichel wrote:
> > This adds device tree support for the tsc2005 touchscreen
> > controller, which is currently only used by the Nokia N900
> > board.
> >
> > The patch does not
On Friday 30 May 2014 22:29:13 Hiroshi Doyu wrote:
>
> IIUC the original problem, "a master with 8 streamIDs" means something
> like below, where some devices have multiple IDs but some have a
> single. A sinle #address-cells cannot afford those 2 masters at once.
>
>iommu {
>
On Wed, May 28, 2014 at 21:45:41 -0400, Naoya Horiguchi wrote:
> > The user could also mark more than
> > one thread in this way - in which case the kernel will pick
> > the first one it sees (is that oldest, or newest?) that is marked.
> > Not sure if this would ever be useful unless you want to
On Friday 30 May 2014 14:31:55 Rob Herring wrote:
> On Fri, May 30, 2014 at 2:06 PM, Arnd Bergmann wrote:
> > On Friday 30 May 2014 08:16:05 Rob Herring wrote:
> >> On Fri, May 23, 2014 at 3:33 PM, Thierry Reding
> >> wrote:
> >> > From: Thierry Reding
> >> > +IOMMU master node:
> >> > +
On 05/30/2014 09:00 AM, Matthew Wilcox wrote:
> On Thu, May 29, 2014 at 11:51:25PM +0200, Matias Bjørling wrote:
>> -static int nvme_map_bio(struct nvme_queue *nvmeq, struct nvme_iod *iod,
>> -struct bio *bio, enum dma_data_direction dma_dir, int psegs)
>> +static int nvme_map_rq(struct
On Fri, 30 May 2014, Vincent Guittot wrote:
> On 30 May 2014 15:26, Dietmar Eggemann wrote:
> >> + /*
> >> + * The group capacity is reduced probably because of activity from
> >> other
> >
> > Here 'group capacity' refers to sgs->group_power and not to
> > sgs->group_capacity, right?
>
On 05/29/2014 08:32 AM, Guenter Roeck wrote:
On 05/28/2014 09:36 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.41 release.
There are 86 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being appli
On 05/29/2014 08:18 AM, Greg Kroah-Hartman wrote:
On Thu, May 29, 2014 at 03:59:23PM +1000, NeilBrown wrote:
On Wed, 28 May 2014 21:32:19 -0700 Greg Kroah-Hartman
wrote:
This is the start of the stable review cycle for the 3.14.5 release.
There are 140 patches in this series, all will be post
On 05/29/2014 07:48 AM, Jiri Slaby wrote:
This is the start of the stable review cycle for the 3.12.21 release.
There are 103 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by
On 05/30/2014 12:32 PM, Tim Chen wrote:
On Fri, 2014-05-30 at 11:45 -0700, Dirk Brandewie wrote:
With turbostat from rc7.
[root@echolake turbostat]# ./turbostat
Core CPU Avg_MHz %Busy Bzy_MHz TSC_MHz SMI CPU%c1 CPU%c3
CPU%c6 CPU%c7 CoreTmp PkgTmp Pkg%pc2 Pkg%pc3 Pkg%pc6 Pk
Implement and enable context tracking for arm64 (which is
a prerequisite for FULL_NOHZ support). This patchset
builds upon earlier work by Kevin Hilman and is based on
Will Deacon's tree.
Changes v6 to v7:
* Rename parameter of ct_user_exit from restore to syscall
Changes v5 to v6:
* Don't save
Make calls to ct_user_enter when the kernel is exited
and ct_user_exit when the kernel is entered (in el0_da,
el0_ia, el0_svc, el0_irq and all of the "error" paths).
These macros expand to function calls which will only work
properly if el0_sync and related code has been rearranged
(in a previous
On 05/30/2014 06:48 PM, Keith Busch wrote:
> On Thu, 29 May 2014, Matias Bjørling wrote:
>> This converts the current NVMe driver to utilize the blk-mq layer.
>
> I'm pretty darn sure this new nvme_remove can cause a process
> with an open reference to use queues after they're freed in the
> nvme_
To implement the context tracker properly on arm64,
a function call needs to be made after debugging and
interrupts are turned on, but before the lr is changed
to point to ret_to_user(). If the function call
is made after the lr is changed the function will not
return to the correct place.
For sim
On Fri, 2014-05-30 at 11:45 -0700, Dirk Brandewie wrote:
>
> With turbostat from rc7.
> [root@echolake turbostat]# ./turbostat
> Core CPU Avg_MHz %Busy Bzy_MHz TSC_MHz SMI CPU%c1 CPU%c3
> CPU%c6 CPU%c7 CoreTmp PkgTmp Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 PkgWatt
> CorWatt GFXWatt
On Fri, May 30, 2014 at 2:06 PM, Arnd Bergmann wrote:
> On Friday 30 May 2014 08:16:05 Rob Herring wrote:
>> On Fri, May 23, 2014 at 3:33 PM, Thierry Reding
>> wrote:
>> > From: Thierry Reding
>> > +IOMMU master node:
>> > +==
>> > +
>> > +Devices that access memory through an IO
On Fri 2014-05-30 17:44:26, Miguel Oliveira wrote:
> Inserted a blank line after a declaration.
>
> Signed-off-by: Miguel Oliveira
Acked-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
Arnd Bergmann writes:
>> > +Multiple-master IOMMU:
>> > +--
>> > +
>> > + iommu {
>> > + /* the specifier represents the ID of the master */
>> > + #address-cells = <1>;
>> > + #size-cells = <0>;
>> > + };
>> > +
>> > +
On Fri, 30 May 2014, Rob Herring wrote:
> There's work in flight to support early_ioremap, early console, and RO
> text patching which all use the fixmap region.
>
> There's a couple of options to solve this:
>
> - Only support up to 16 cpus. It could be anywhere between 17-31, but
> that seems
On 30 May 2014 15:26, Dietmar Eggemann wrote:
> On 23/05/14 16:53, Vincent Guittot wrote:
>> If the CPU is used for handling lot of IRQs, trig a load balance to check if
>> it's worth moving its tasks on another CPU that has more capacity
>>
>> Signed-off-by: Vincent Guittot
>> ---
>> kernel/sch
> > Would you mind telling me what I have changed that affects drivers
> > registering via Sysfs?
>
> Check Documentation/i2c/instantiating-devices, method 4. If a driver
> does not have i2c_device_id, then this method won't work because the
> newly created device has no of_node or ACPI_node and n
On 30 May 2014 11:50, Dietmar Eggemann wrote:
> On 23/05/14 16:53, Vincent Guittot wrote:
>> Monitor the activity level of each group of each sched_domain level. The
>> activity is the amount of cpu_power that is currently used on a CPU or group
>> of CPUs. We use the runnable_avg_sum and _period
Hi all,
On Fri, May 30, 2014 at 10:16 PM, Sachin Kamat wrote:
>
>
> On Friday, 30 May 2014, Tushar Behera wrote:
>>
>> On Thu, May 29, 2014 at 11:30 PM, Andreas Färber wrote:
>> > Hi Tarek,
>> >
>> >
>> > And I reproducibly get failures for CPUs 1-3, resulting in only one CPU
>> > in /proc/cpui
On 30 May 2014 08:34, Peter Zijlstra wrote:
> On Thu, May 29, 2014 at 09:56:24PM +0200, Vincent Guittot wrote:
>> On 29 May 2014 16:02, Peter Zijlstra wrote:
>> > On Fri, May 23, 2014 at 05:53:05PM +0200, Vincent Guittot wrote:
>> >> @@ -6052,8 +6006,8 @@ static inline void update_sd_lb_stats(str
On Fri, 2014-05-30 at 21:24 +0300, Dmitry Kasatkin wrote:
> On 30 May 2014 20:58, "Mimi Zohar" wrote:
> >
> > On Fri, 2014-05-30 at 18:58 +0300, Dmitry Kasatkin wrote:
> > > On 28 May 2014 18:09, Mimi Zohar wrote:
> > > > Dot prefixed keyring names are supposed to be reserved for the
> > > > ker
On Friday 30 May 2014 12:27:28 Dave Martin wrote:
> On Fri, May 30, 2014 at 08:30:08AM +0100, Thierry Reding wrote:
> > On Thu, May 29, 2014 at 09:52:22AM -0600, Stephen Warren wrote:
> > > On 05/23/2014 02:36 PM, Thierry Reding wrote:
> > > I think this is a mistake. address-cells/size-cells are f
Hi,
On Fri, May 30, 2014 at 7:41 AM, Tushar Behera wrote:
> On Thu, May 29, 2014 at 11:30 PM, Andreas Färber wrote:
>> Hi Tarek,
>>
>>
>> And I reproducibly get failures for CPUs 1-3, resulting in only one CPU
>> in /proc/cpuinfo (compared to 4 on downstream 3.14):
>>
>> [0.045778] CPU: Test
On Friday 30 May 2014 08:16:05 Rob Herring wrote:
> On Fri, May 23, 2014 at 3:33 PM, Thierry Reding
> wrote:
> > From: Thierry Reding
> > +IOMMU master node:
> > +==
> > +
> > +Devices that access memory through an IOMMU are called masters. A device
> > can
> > +have multiple mas
WARNING: CPU: 1 PID: 24000 at lib/dma-debug.c:593
debug_dma_assert_idle+0x1a4/0x220()
i915 :00:02.0: DMA-API: cpu touching an active dma mapped cacheline
[cln=0x04401d40]
Modules linked in: ccm ip6t_rpfilter ip6t_REJECT xt_conntrack ebtable_nat
ebtable_broute bridge stp llc ebtable_f
On Friday 30 May 2014 12:22:32 Dave Martin wrote:
> > +
> > +Examples:
> > +=
> > +
> > +Single-master IOMMU:
> > +
> > +
> > + iommu {
> > + #address-cells = <0>;
> > + #size-cells = <0>;
> > + };
> > +
> > + master {
> > + iommus = <
On 05/30/2014 10:56 AM, Tim Chen wrote:
> On Thu, 2014-05-29 at 21:16 -0400, Dave Jones wrote:
>> On Thu, May 29, 2014 at 06:07:16PM -0700, Tim Chen wrote:
>> > On Thu, 2014-05-29 at 19:54 -0400, George Spelvin wrote:
>> > > Sorry for the delay; my Ivy Bridge test machine isn't in my
>> > > o
On Fri, May 30, 2014 at 11:20:05AM -0700, Thomas Wood wrote:
> When using scripts/checkpatch.pl, there are errors about trailing whitespace.
> Use scripts/cleanfile to remove these errors.
>
Someone already fixed these. Work against linux-next.
regards,
dan carpenter
--
To unsubscribe from th
On Thu, May 29, 2014 at 10:45:04PM +0100, Larry Bassel wrote:
> Make calls to ct_user_enter when the kernel is exited
> and ct_user_exit when the kernel is entered (in el0_da,
> el0_ia, el0_svc, el0_irq and all of the "error" paths).
>
> These macros expand to function calls which will only work
>
On Tue, May 27, 2014 at 06:18:42PM +0800, Kefeng Wang wrote:
> Use devm_ioremap_resource() to make the code simpler, drop unused variable,
> redundant return value check, and error-handing code.
>
> Signed-off-by: Kefeng Wang
> ---
> drivers/iommu/msm_iommu_dev.c | 38 +++--
On Thu, May 29, 2014 at 03:45:47PM +0200, Paul Bolle wrote:
> On Mon, 2014-05-26 at 11:39 +0200, Joerg Roedel wrote:
> > On Fri, May 16, 2014 at 03:39:40PM +0800, Vaughan Cao wrote:
> > > amd_iommu_rlookup_table[devid] != NULL is already guaranteed by
> > > check_device
> > > called before, it's f
On Thu, May 29, 2014 at 10:45:03PM +0100, Larry Bassel wrote:
> To implement the context tracker properly on arm64,
> a function call needs to be made after debugging and
> interrupts are turned on, but before the lr is changed
> to point to ret_to_user(). If the function call
> is made after the l
When using scripts/checkpatch.pl, there are errors about trailing whitespace.
Use scripts/cleanfile to remove these errors.
Signed-off-by: Thomas Wood
---
drivers/staging/goldfish/goldfish_nand.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/goldfi
On 05/30/2014 07:33 PM, David Daney wrote:
On 05/30/2014 04:39 AM, Geert Uytterhoeven wrote:
On Fri, May 30, 2014 at 1:30 PM, abdoulaye berthe
wrote:
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpiolib.c
@@ -1263,10 +1263,9 @@ static void gpiochip_irqchip_remove(struct
gpio_chip *gpiochip)
On Fri, 2014-05-30 at 16:34 +0800, Weijie Yang wrote:
> Currently, we use a rwlock tb_lock to protect concurrent access to
> the whole zram meta table. However, according to the actual access model,
> there is only a small chance for upper user to access the same table[index],
> so the current lock
On 05/30/2014 10:24 AM, Dave Hansen wrote:
> On 05/30/2014 09:06 AM, Linus Torvalds wrote:
>> On Fri, May 30, 2014 at 8:52 AM, H. Peter Anvin wrote:
That said, it's still likely a non-production option due to the page
table games we'd have to play at fork/clone time.
>>>
>>> Still, seems
On 05/30/14 20:52, Tomasz Figa wrote:
On 26.05.2014 08:29, Chanwoo Choi wrote:
This patch add pmusysreg node for Exynos3250 to access PMU (Power Management
Unit)
register in a centralized way using syscon driver.
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
---
Documentation/devicetre
On May 30, 2014, at 12:28 PM, Stephen Boyd wrote:
> On 05/29/14 09:26, Kumar Gala wrote:
>> Signed-off-by: Kumar Gala
>> ---
>> arch/arm/configs/qcom_defconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm/configs/qcom_defconfig
>> b/arch/arm/configs/qcom_defconfig
>> in
On 30 May 2014 11:25, Rob Herring wrote:
> On Fri, May 30, 2014 at 8:43 AM, wrote:
>> From: Pratik Patel
>>
>> CoreSight components are compliant with the ARM CoreSight
>> architecture specification and can be connected in various
>> topologies to suite a particular SoCs tracing needs. These tr
On Fri, May 30, 2014 at 04:33:46PM +0100, Rob Herring wrote:
> On Tue, Apr 15, 2014 at 6:06 AM, Liu Hua wrote:
> > In 32-bit ARM systems, the fixmap mapping region can support
> > no more than 14 CPUs(total: 896k; one CPU: 64K). And we can
> > configure NR_CPUS up to 32. So there is a mismatch.
>
Hey, Vivek.
On Fri, May 30, 2014 at 01:55:27PM -0400, Vivek Goyal wrote:
> Now CFQ also dynamically adjusts the slice length based on the how
> many queues are ready to do IO. One problem with fixed slice lenth
> round robin was that if there are lot of queues doing IO, then after
> serving one qu
On Fri, 2014-05-30 at 18:58 +0300, Dmitry Kasatkin wrote:
> On 28 May 2014 18:09, Mimi Zohar wrote:
> > Dot prefixed keyring names are supposed to be reserved for the
> > kernel, but add_key() calls key_get_type_from_user(), which
> > incorrectly verifies the 'type' field, not the 'description' f
On Thu, 2014-05-29 at 21:16 -0400, Dave Jones wrote:
> On Thu, May 29, 2014 at 06:07:16PM -0700, Tim Chen wrote:
> > On Thu, 2014-05-29 at 19:54 -0400, George Spelvin wrote:
> > > Sorry for the delay; my Ivy Bridge test machine isn't in my
> > > office and getting to the console to tweak the BIO
On Fri, May 30, 2014 at 01:26:09PM -0400, Tejun Heo wrote:
> Hello,
>
> On Fri, May 30, 2014 at 01:09:58PM -0400, Vivek Goyal wrote:
> > Are you referring to BFQ paper. I had read one in the past and it was
> > all about how to achieve more accurate fairness. At this point of time
> > I don't thin
Hi Lee,
sorry for the delay.
> Would you mind telling me what I have changed that affects drivers
> registering via Sysfs?
Check Documentation/i2c/instantiating-devices, method 4. If a driver
does not have i2c_device_id, then this method won't work because the
newly created device has no of_node
On Fri, May 30, 2014 at 01:31:46PM -0400, Vivek Goyal wrote:
> > What allows BFQ to provide the above features is its accurate
> > scheduling engine (patches 1-4), combined with a set of simple
> > heuristics and improvements (patches 5-14).
>
> This is very hard to understand. This puzzle need t
Fixing compiler error with some gcc version(s) that do not
support __builtin_log2(). Replacing __builtin_log2() with
ilog2().
Signed-off-by: T. Makphaibulchoke
---
fs/mbcache.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/mbcache.c b/fs/mbcache.c
index bf166e3..18747
On 05/30/2014 04:39 AM, Geert Uytterhoeven wrote:
On Fri, May 30, 2014 at 1:30 PM, abdoulaye berthe wrote:
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpiolib.c
@@ -1263,10 +1263,9 @@ static void gpiochip_irqchip_remove(struct gpio_chip
*gpiochip);
*
* A gpio_chip with any GPIOs stil
On Tue, May 27, 2014 at 02:42:24PM +0200, paolo wrote:
> From: Paolo Valente
>
> [Re-posting, previous attempt seems to have partially failed]
>
> Hi,
> this patchset introduces the last version of BFQ, a proportional-share
> storage-I/O scheduler. BFQ also supports hierarchical scheduling with
On 05/29/14 09:26, Kumar Gala wrote:
> Signed-off-by: Kumar Gala
> ---
> arch/arm/configs/qcom_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/configs/qcom_defconfig b/arch/arm/configs/qcom_defconfig
> index bfed753..42ebd72 100644
> --- a/arch/arm/configs/qcom_defconf
On Thursday, May 29, 2014 9:44 PM, Chase Southwood wrote:
> Move the function apci1564_interrupt() from hwdrv_apci1564.c to
> addi_apci_1564.c. On moving, for now just strip out all of the
> code for interrupts that the driver does not yet support at this
> time.
>
> Rename the variable ui_Interru
> This patchset is the summary of recent discussion about memory error handling
> on multithread application. Patch 1 and 2 is for action required errors, and
> patch 3 is for action optional errors.
Naoya,
You suggested early in the discussion (when there were just two patches) that
they deserve
Hello,
On Fri, May 30, 2014 at 01:09:58PM -0400, Vivek Goyal wrote:
> Are you referring to BFQ paper. I had read one in the past and it was
> all about how to achieve more accurate fairness. At this point of time
> I don't think that smarter algorithm is the problem. Until and unless
> somebody ca
Acked-by: Dimitri Sivanich
On Fri, May 30, 2014 at 03:40:59PM +0200, Manuel Schölling wrote:
> To be future-proof and for better readability the time comparisons are
> modified to use time_before() instead of plain, error-prone math.
>
> Signed-off-by: Manuel Schölling
> ---
> drivers/misc/sgi
On Fri, May 30, 2014 at 8:43 AM, wrote:
> From: Pratik Patel
>
> CoreSight components are compliant with the ARM CoreSight
> architecture specification and can be connected in various
> topologies to suite a particular SoCs tracing needs. These trace
> components can generally be classified as s
On 05/30/2014 09:06 AM, Linus Torvalds wrote:
> On Fri, May 30, 2014 at 8:52 AM, H. Peter Anvin wrote:
>>> That said, it's still likely a non-production option due to the page
>>> table games we'd have to play at fork/clone time.
>>
>> Still, seems much more tractable.
>
> We might be able to mak
Now with the attachment... :)
On Fri 30-05-14 19:23:27, Jan Kara wrote:
> On Fri 30-05-14 18:58:10, Jan Kara wrote:
> > On Fri 30-05-14 18:19:48, Peter Zijlstra wrote:
> > > On Fri, May 30, 2014 at 06:16:47PM +0200, Peter Zijlstra wrote:
> > > > On Fri, May 30, 2014 at 05:50:51PM +0200, Jan Kara
On Fri 30-05-14 18:58:10, Jan Kara wrote:
> On Fri 30-05-14 18:19:48, Peter Zijlstra wrote:
> > On Fri, May 30, 2014 at 06:16:47PM +0200, Peter Zijlstra wrote:
> > > On Fri, May 30, 2014 at 05:50:51PM +0200, Jan Kara wrote:
> > > > > [7.492350] ==
On 05/30/2014 01:12 AM, Jens Axboe wrote:
> On 05/29/2014 05:06 PM, Jens Axboe wrote:
>> Ah I see, yes that code apparently got axed. The attached patch brings
>> it back. Totally untested, I'll try and synthetically hit it to ensure
>> that it does work. Note that it currently does unmap and iod f
On 05/30/14 15:45, Paolo Bonzini wrote:
> I was thinking of removing it in Linux 3.17. I'm not even sure it
> compiles right now, hasn't seen any action in years, and all open-source
> userspace code to use it has been dead for years.
>
> If you disagree, please speak up loudly in the next month.
From: Srinivas Kandagatla
On some SOCs like Qcom there are explicit bits in the command register
to specify if its a data transfer command or not. So this patch adds
support to such bits in variant data, giving more flexibility to the
driver.
Signed-off-by: Srinivas Kandagatla
Reviewed-by: Linu
On Fri, May 30, 2014 at 6:48 PM, Al Viro wrote:
> On Fri, May 30, 2014 at 08:31:30AM -0700, Linus Torvalds wrote:
>> On Fri, May 30, 2014 at 8:21 AM, Al Viro wrote:
>> >
>> > Linus, how would you prefer it to be handled?
>>
>> I'll just have to do an rc8. I really hoped to avoid it, because we're
From: Srinivas Kandagatla
This patch adds a fake Qualcomm ID 0x00051180 to the amba_ids, as Qualcomm
SDCC controller is pl180, but amba id registers read 0x0's.
The plan is to remove SDCC driver totally and use mmci as the main SD
controller driver for Qualcomm SOCs.
Signed-off-by: Srinivas Kand
From: Srinivas Kandagatla
MCIFIFOCNT register behaviour on Qcom chips is very different than the other
pl180 integrations. MCIFIFOCNT register contains the number of
words that are still waiting to be transferred through the FIFO. It keeps
decrementing once the host CPU reads the MCIFIFO. With th
On 05/29/2014 02:27 PM, Linus Torvalds wrote:
On Thu, May 29, 2014 at 2:07 PM, Guenter Roeck wrote:
On Thu, May 29, 2014 at 11:21:09AM -0700, Greg Kroah-Hartman wrote:
On Thu, May 29, 2014 at 08:06:10AM -0700, Guenter Roeck wrote:
alpha:defconfig - Fails with 'Inconsisten
From: Srinivas Kandagatla
On Controllers like Qcom SD card controller where cclk is mclk and mclk should
be directly controlled by the driver.
This patch adds support to control mclk directly in the driver, and also
adds explicit_mclk_control flag in variant structure giving more flexibility
to
From: Srinivas Kandagatla
Some of the controller have maximum supported frequency, This patch adds
support in variant data structure to specify such restrictions. This
gives more flexibility in calculating the f_max before passing it to
mmc-core.
Signed-off-by: Srinivas Kandagatla
---
drivers/
From: Srinivas Kandagatla
This patch adds edge support for data and command out to variant structure
giving more flexibility to the driver to support more SOCs which have
different clock register layout.
Without this patch other new SOCs like Qcom will have to add more code to
special case them
On Fri, May 30, 2014 at 05:48:16PM +0100, Al Viro wrote:
> On Fri, May 30, 2014 at 08:31:30AM -0700, Linus Torvalds wrote:
> > On Fri, May 30, 2014 at 8:21 AM, Al Viro wrote:
> > >
> > > Linus, how would you prefer it to be handled?
> >
> > I'll just have to do an rc8. I really hoped to avoid it,
From: Srinivas Kandagatla
Instance of this IP on Qualcomm's SOCs has bit different layout for datactrl
register. Bit position datactrl[16:4] hold the true block size instead of power
of 2.
Signed-off-by: Srinivas Kandagatla
Reviewed-by: Linus Walleij
---
drivers/mmc/host/mmci.c | 5 +
1 f
From: Srinivas Kandagatla
This patch adds 8bit bus enable to variant structure giving more flexibility
to the driver to support more SOCs which have different clock register layout.
Without this patch other new SOCs like Qcom will have to add more code
to special case them.
Signed-off-by: Srini
From: Srinivas Kandagatla
This patch adds a Qualcomm SD Card controller specific register variations
to header file. Qualcomm SDCC controller is pl180, with slight changes in
the register layout from standard pl180 register set.
Signed-off-by: Srinivas Kandagatla
---
drivers/mmc/host/mmci.h |
From: Srinivas Kandagatla
This patch adds ddrmode mask to variant structure giving more flexibility
to the driver to support more SOCs which have different datactrl register
layout.
Without this patch datactrl register is updated with incorrect ddrmode mask,
resulting in failures on Qualcomm SD
From: Srinivas Kandagatla
On Qcom SD Card controller POWER, CLKCTRL, DATACTRL and COMMAND registers
should be updated in MCLK domain, and writes to these registers must be
separated by three MCLK cycles. This resitriction is not applicable for
other registers. Any subsequent writes to these regis
From: Srinivas Kandagatla
This patch converts the register bits in the header file to use BIT(()
macro, which looks much neater.
No functional changes done.
Signed-off-by: Srinivas Kandagatla
---
drivers/mmc/host/mmci.h | 208
1 file changed, 1
From: Srinivas Kandagatla
This patch replaces a constant used in calculating timeout with a proper
macro. This is make code more readable.
Signed-off-by: Srinivas Kandagatla
Reviewed-by: Linus Walleij
---
drivers/mmc/host/mmci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --gi
From: Srinivas Kandagatla
Thankyou Linus W, Ulf H and everyone for reviewing RFC to v4 patches.
This patch series adds Qualcomm SD Card Controller support in pl180 mmci
driver. QCom SDCC is basically a pl180, but bit more customized, some of the
register layouts and offsets are different to the
On Fri, May 30, 2014 at 12:16:50PM -0400, Tejun Heo wrote:
> Hello, Vivek.
>
> On Fri, May 30, 2014 at 11:32:28AM -0400, Vivek Goyal wrote:
> > I don't think most of the people care about strong fairness guarantee.
> > As an algorithm round robin is not bad for ensuring fairness. CFQ had
> > start
On Fri, 30 May 2014 10:02:23 -0400
Steven Rostedt wrote:
> This last part conflicts with my current 3.16 queue. You can see how it
> does in my for-next repo. But I'll be pushing my latest with the
> updates I mentioned above soon and will let you know where to get them.
I just pushed my updates
(memdup_user can be used to replace kmalloc/copy_from_user. Not sure if it's ok
with kzalloc ...)
Cc: linux-s...@vger.kernel.org
Cc: Anil Gurumurthy
Cc: "James E.J. Bottomley"
Signed-off-by: Fabian Frederick
---
drivers/scsi/bfa/bfad_debugfs.c | 30 ++
1 file chang
On 05/30/2014 06:27 AM, Manuel Schölling wrote:
> ---
> drivers/video/console/Kconfig |6 +-
> drivers/video/console/vgacon.c | 124
>
> 2 files changed, 79 insertions(+), 51 deletions(-)
>
> diff --git a/drivers/video/console/Kconfig b/drivers/vide
On Fri, 2014-05-30 at 12:52 -0400, George Spelvin wrote:
> > That's very small (less than 0.2%) so I think it's acceptable.
>
> Thank you! May I take this as an Acked-by; ?
Yes, with the caveat that you still have a v3 of this patch
that reorganize the K table to rodata.
Tim
>
> I'll work on s
On Tue, May 07, 2013 at 04:29:31PM -0700, Yinghai Lu wrote:
> We should assign unassigned resource before pci_bus_add_device.
>
> as late one will enable driver and create sysfs file that will need
> pci io resources from assign unassigned code.
>
> Signed-off-by: Yinghai Lu
Applied to pci/reso
201 - 300 of 698 matches
Mail list logo
