On Fri, 2014-01-10 at 15:11 +0800, Baoquan wrote:
> On 01/09/14 at 02:56pm, Toshi Kani wrote:
:
> > I am more curious to know how makedumpfile decides what memory ranges to
> > dump. The 1st kernel may have performed memory hot-add / delete
> > operations before a crash, so it needs to know the v
On Fri, 2014-01-10 at 17:14 +0800, Baoquan wrote:
:
> >
> > >Otherwise, any hotplug memory which is not reserved for 2nd kernel can
> > >be parsed and need be added as hotplug memory, and add them into movable
> > >zone.
> >
> > wrong.
> > The memory is allocated as normal zone and it is offline
On 01/10/14 at 06:35pm, Yasuaki Ishimatsu wrote:
> (2014/01/10 18:14), Baoquan wrote:
> >
> > >In ns
> >>>object tree, they are not treated as hotplug memory.
> >>
> >>wrong.
> >>They are treated as hotplug memory. But the memory cannot hot removed
> >>because the memory has kernel memory.
> >>
>
(2014/01/10 18:14), Baoquan wrote:
>In ns
object tree, they are not treated as hotplug memory.
wrong.
They are treated as hotplug memory. But the memory cannot hot removed
because the memory has kernel memory.
Otherwise, any hotplug memory which is not reserved for 2nd kernel can
be parse
>In ns
> >object tree, they are not treated as hotplug memory.
>
> wrong.
> They are treated as hotplug memory. But the memory cannot hot removed
> because the memory has kernel memory.
>
> >Otherwise, any hotplug memory which is not reserved for 2nd kernel can
> >be parsed and need be added as
(2014/01/10 16:11), Baoquan wrote:
On 01/09/14 at 02:56pm, Toshi Kani wrote:
On Thu, 2014-01-09 at 16:27 -0500, Vivek Goyal wrote:
On Thu, Jan 09, 2014 at 11:34:30AM -0700, Toshi Kani wrote:
On Thu, 2014-01-09 at 13:23 -0500, Vivek Goyal wrote:
On Thu, Jan 09, 2014 at 10:24:25AM -0700, Toshi
On 01/09/14 at 02:56pm, Toshi Kani wrote:
> On Thu, 2014-01-09 at 16:27 -0500, Vivek Goyal wrote:
> > On Thu, Jan 09, 2014 at 11:34:30AM -0700, Toshi Kani wrote:
> > > On Thu, 2014-01-09 at 13:23 -0500, Vivek Goyal wrote:
> > > > On Thu, Jan 09, 2014 at 10:24:25AM -0700, Toshi Kani wrote:
> > > >
On Thursday, January 09, 2014 11:34:30 AM Toshi Kani wrote:
> On Thu, 2014-01-09 at 13:23 -0500, Vivek Goyal wrote:
> > On Thu, Jan 09, 2014 at 10:24:25AM -0700, Toshi Kani wrote:
> >
> > [..]
> > > > I think creating a new command line option is simpler as compared to
> > > > creating a new flag
On Thu, 2014-01-09 at 16:27 -0500, Vivek Goyal wrote:
> On Thu, Jan 09, 2014 at 11:34:30AM -0700, Toshi Kani wrote:
> > On Thu, 2014-01-09 at 13:23 -0500, Vivek Goyal wrote:
> > > On Thu, Jan 09, 2014 at 10:24:25AM -0700, Toshi Kani wrote:
> > >
> > > [..]
> > > > > I think creating a new command
On Thu, Jan 09, 2014 at 11:34:30AM -0700, Toshi Kani wrote:
> On Thu, 2014-01-09 at 13:23 -0500, Vivek Goyal wrote:
> > On Thu, Jan 09, 2014 at 10:24:25AM -0700, Toshi Kani wrote:
> >
> > [..]
> > > > I think creating a new command line option is simpler as compared to
> > > > creating a new flag
On Thu, 2014-01-09 at 13:23 -0500, Vivek Goyal wrote:
> On Thu, Jan 09, 2014 at 10:24:25AM -0700, Toshi Kani wrote:
>
> [..]
> > > I think creating a new command line option is simpler as compared to
> > > creating a new flag in bootparam which in turn disables memory hotplug.
> > > More users can
On Thu, Jan 09, 2014 at 10:24:25AM -0700, Toshi Kani wrote:
[..]
> > I think creating a new command line option is simpler as compared to
> > creating a new flag in bootparam which in turn disables memory hotplug.
> > More users can use that option. For example, if for some reason hotplug
> > code
On Thu, 2014-01-09 at 11:24 -0500, Vivek Goyal wrote:
> On Thu, Jan 09, 2014 at 09:03:59AM -0700, Toshi Kani wrote:
>
> [..]
> > > > > > So basically acpi thinks that some memory block is a hot plug memory
> > > > > > and tries to add it. And that consumes lots of memory and we don't
> > > > > >
On Thu, Jan 09, 2014 at 09:03:59AM -0700, Toshi Kani wrote:
[..]
> > > > > So basically acpi thinks that some memory block is a hot plug memory
> > > > > and tries to add it. And that consumes lots of memory and we don't
> > > > > have
> > > > > that memory in second kernel.
> > > >
> > > > That
On Thu, 2014-01-09 at 09:53 -0500, Vivek Goyal wrote:
> On Thu, Jan 09, 2014 at 02:10:26PM +0100, Rafael J. Wysocki wrote:
> > On Wednesday, January 08, 2014 05:11:48 PM Toshi Kani wrote:
> > > On Thu, 2014-01-09 at 00:07 +0100, Rafael J. Wysocki wrote:
> > > > On Wednesday, January 08, 2014 10:58:
On Thu, 2014-01-09 at 09:50 -0500, Vivek Goyal wrote:
> On Wed, Jan 08, 2014 at 05:11:48PM -0700, Toshi Kani wrote:
> > On Thu, 2014-01-09 at 00:07 +0100, Rafael J. Wysocki wrote:
> > > On Wednesday, January 08, 2014 10:58:29 AM Vivek Goyal wrote:
> > > > On Wed, Jan 08, 2014 at 11:26:43PM +0800, B
On Thu, Jan 09, 2014 at 02:10:26PM +0100, Rafael J. Wysocki wrote:
> On Wednesday, January 08, 2014 05:11:48 PM Toshi Kani wrote:
> > On Thu, 2014-01-09 at 00:07 +0100, Rafael J. Wysocki wrote:
> > > On Wednesday, January 08, 2014 10:58:29 AM Vivek Goyal wrote:
> > > > On Wed, Jan 08, 2014 at 11:26
On Wed, Jan 08, 2014 at 05:11:48PM -0700, Toshi Kani wrote:
> On Thu, 2014-01-09 at 00:07 +0100, Rafael J. Wysocki wrote:
> > On Wednesday, January 08, 2014 10:58:29 AM Vivek Goyal wrote:
> > > On Wed, Jan 08, 2014 at 11:26:43PM +0800, Baoquan wrote:
> > >
> > > [..]
> > > > [1.59] acpi PN
On Thu, Jan 09, 2014 at 12:07:17AM +0100, Rafael J. Wysocki wrote:
> On Wednesday, January 08, 2014 10:58:29 AM Vivek Goyal wrote:
> > On Wed, Jan 08, 2014 at 11:26:43PM +0800, Baoquan wrote:
> >
> > [..]
> > > [1.59] acpi PNP0A03:03: fail to add MMCONFIG information, can't
> > > access e
On Wednesday, January 08, 2014 05:11:48 PM Toshi Kani wrote:
> On Thu, 2014-01-09 at 00:07 +0100, Rafael J. Wysocki wrote:
> > On Wednesday, January 08, 2014 10:58:29 AM Vivek Goyal wrote:
> > > On Wed, Jan 08, 2014 at 11:26:43PM +0800, Baoquan wrote:
> > >
> > > [..]
> > > > [1.59] acpi P
On 01/09/14 at 12:07am, Rafael J. Wysocki wrote:
> On Wednesday, January 08, 2014 10:58:29 AM Vivek Goyal wrote:
> > On Wed, Jan 08, 2014 at 11:26:43PM +0800, Baoquan wrote:
> >
> > [..]
> > > [1.59] acpi PNP0A03:03: fail to add MMCONFIG information, can't
> > > access extended PCI config
On Thu, 2014-01-09 at 00:07 +0100, Rafael J. Wysocki wrote:
> On Wednesday, January 08, 2014 10:58:29 AM Vivek Goyal wrote:
> > On Wed, Jan 08, 2014 at 11:26:43PM +0800, Baoquan wrote:
> >
> > [..]
> > > [1.59] acpi PNP0A03:03: fail to add MMCONFIG information, can't
> > > access extended
On Wednesday, January 08, 2014 10:58:29 AM Vivek Goyal wrote:
> On Wed, Jan 08, 2014 at 11:26:43PM +0800, Baoquan wrote:
>
> [..]
> > [1.59] acpi PNP0A03:03: fail to add MMCONFIG information, can't
> > access extended PCI configuration space under this bridge.
> > [1.605045] PCI host
On Wed, Jan 08, 2014 at 11:26:43PM +0800, Baoquan wrote:
[..]
> [1.59] acpi PNP0A03:03: fail to add MMCONFIG information, can't
> access extended PCI configuration space under this bridge.
> [1.605045] PCI host bridge to bus :ff
> [1.609615] pci_bus :ff: root bus resource
24 matches
Mail list logo
