On Fri, Jan 11, 2013 at 2:57 AM, Vasilis Liaskovitis
wrote:
>> >
>> > IIRC q35 supports memory hotplug natively (picked up in some
>> > discussion). Is that correct?
>> >
>> From previous discussion I also understand that q35 supports native hotplug.
>> Sections 5.1 and 5.2 of the spec describe t
On Thu, Mar 28, 2013 at 5:29 PM, Vasilis Liaskovitis
wrote:
> Hi,
>
> [...]
>>> > >
>>> > > I haven't updated the series for a while, but I can rework if there is
>>> > > a more
>>> > > clear direction for the community.
>>> > >
>>> > > Another open issue is reference counting of memoryregions in
Hi,
[...]
>> > >
>> > > I haven't updated the series for a while, but I can rework if there is a
>> > > more
>> > > clear direction for the community.
>> > >
>> > > Another open issue is reference counting of memoryregions in qemu memory
>> > > model. In order to make memory hot-remove operations
在 2013-03-26二的 11:20 -0300，Eduardo Habkost写道：
> On Wed, Mar 20, 2013 at 02:18:00PM +0800, li guang wrote:
> > 在 2013-01-09三的 01:08 +0100，Andreas Färber写道：
> > > Am 18.12.2012 13:41, schrieb Vasilis Liaskovitis:
> > > > Because dimm layout needs to be configured on machine-boot, all dimm
> > > > de
在 2013-03-26二的 17:43 +0100，Vasilis Liaskovitis写道：
> Hi,
>
> On Tue, Mar 19, 2013 at 03:28:38PM +0800, li guang wrote:
> [...]
> > > > > This is v4 of the ACPI memory hotplug functionality. Only x86_64
> > > > > target is
> > > > > supported (both i440fx and q35). There are still several issues, b
在 2013-03-26二的 17:58 +0100，Vasilis Liaskovitis写道：
> Hi,
>
> On Tue, Mar 19, 2013 at 02:30:25PM +0800, li guang wrote:
> > 在 2013-01-10四的 19:57 +0100，Vasilis Liaskovitis写道：
> > > > >
> > > > > IIRC q35 supports memory hotplug natively (picked up in some
> > > > > discussion). Is that correct?
> >
Hi,
On Tue, Mar 26, 2013 at 10:47:01AM -0400, Luiz Capitulino wrote:
> On Tue, 18 Dec 2012 13:41:28 +0100
> Vasilis Liaskovitis wrote:
>
> > This is v4 of the ACPI memory hotplug functionality. Only x86_64 target is
> > supported (both i440fx and q35). There are still several issues, but it's
>
Hi,
On Tue, Mar 19, 2013 at 02:30:25PM +0800, li guang wrote:
> 在 2013-01-10四的 19:57 +0100，Vasilis Liaskovitis写道：
> > > >
> > > > IIRC q35 supports memory hotplug natively (picked up in some
> > > > discussion). Is that correct?
> > > >
> > > From previous discussion I also understand that q35
Hi,
On Tue, Mar 19, 2013 at 03:28:38PM +0800, li guang wrote:
[...]
> > > > This is v4 of the ACPI memory hotplug functionality. Only x86_64 target
> > > > is
> > > > supported (both i440fx and q35). There are still several issues, but
> > > > it's
> > > > been a while since v3 and I wanted to g
On Tue, 18 Dec 2012 13:41:28 +0100
Vasilis Liaskovitis wrote:
> This is v4 of the ACPI memory hotplug functionality. Only x86_64 target is
> supported (both i440fx and q35). There are still several issues, but it's
> been a while since v3 and I wanted to get some more feedback on the current
> st
On Wed, Mar 20, 2013 at 02:18:00PM +0800, li guang wrote:
> 在 2013-01-09三的 01:08 +0100，Andreas Färber写道：
> > Am 18.12.2012 13:41, schrieb Vasilis Liaskovitis:
> > > Because dimm layout needs to be configured on machine-boot, all dimm
> > > devices
> > > need to be specified on startup command line
在 2013-01-09三的 01:08 +0100，Andreas Färber写道：
> Am 18.12.2012 13:41, schrieb Vasilis Liaskovitis:
> > Because dimm layout needs to be configured on machine-boot, all dimm devices
> > need to be specified on startup command line (either with populated=on or
> > with
> > populated=off). The dimm info
在 2013-02-28四的 11:18 +0100，Vasilis Liaskovitis写道：
> Hi,
>
> sorry for the delay.
> On Tue, Feb 19, 2013 at 07:39:40PM -0300, Erlon Cruz wrote:
> > On Tue, Dec 18, 2012 at 10:41 AM, Vasilis Liaskovitis <
> > vasilis.liaskovi...@profitbricks.com> wrote:
> >
> > > This is v4 of the ACPI memory hotpl
在 2013-01-10四的 19:57 +0100，Vasilis Liaskovitis写道：
> > >
> > > IIRC q35 supports memory hotplug natively (picked up in some
> > > discussion). Is that correct?
> > >
> > From previous discussion I also understand that q35 supports native
> > hotplug.
> > Sections 5.1 and 5.2 of the spec describ
Hi,
sorry for the delay.
On Tue, Feb 19, 2013 at 07:39:40PM -0300, Erlon Cruz wrote:
> On Tue, Dec 18, 2012 at 10:41 AM, Vasilis Liaskovitis <
> vasilis.liaskovi...@profitbricks.com> wrote:
>
> > This is v4 of the ACPI memory hotplug functionality. Only x86_64 target is
> > supported (both i440fx
On Tue, Dec 18, 2012 at 10:41 AM, Vasilis Liaskovitis <
vasilis.liaskovi...@profitbricks.com> wrote:
> This is v4 of the ACPI memory hotplug functionality. Only x86_64 target is
> supported (both i440fx and q35). There are still several issues, but it's
> been a while since v3 and I wanted to get
> >
> > IIRC q35 supports memory hotplug natively (picked up in some
> > discussion). Is that correct?
> >
> From previous discussion I also understand that q35 supports native hotplug.
> Sections 5.1 and 5.2 of the spec describe the MCH registers but the native
> memory hotplug specifics are n
Am 10.01.2013 18:36, schrieb Vasilis Liaskovitis:
> Btw, is the CPU link feature already implemented in a qom-cpu branch?
No, the latest topology series moves fields around as preparation.
There's still one CPUState per hyperthread, but as a DeviceState now.
Andreas
--
SUSE LINUX Products GmbH,
Hi,
On Wed, Jan 09, 2013 at 01:08:52AM +0100, Andreas Färber wrote:
> Am 18.12.2012 13:41, schrieb Vasilis Liaskovitis:
> > Because dimm layout needs to be configured on machine-boot, all dimm devices
> > need to be specified on startup command line (either with populated=on or
> > with
> > popula
Am 18.12.2012 13:41, schrieb Vasilis Liaskovitis:
> Because dimm layout needs to be configured on machine-boot, all dimm devices
> need to be specified on startup command line (either with populated=on or with
> populated=off). The dimm information is stored in dimm configuration
> structures.
>
Hi,
> correct, only the number of channels and ranks(dimms) per channel has been
> emulated so far (2 channels of 4 dimms each). So it is still paravirtual
> memory
> hotplug, not native. Native support still needs to be worked on.
Ok.
>> I think the paravirtual memory hotplug controller shou
On Wed, Dec 19, 2012 at 12:45:46AM +0800, Zhi Yong Wu wrote:
> HI,
>
> One stupid question, 'dimm' presents one guest memory, then why it is
> called as "dimm"? what is its full name?
it's a bad name coming from dram technology (dual in-line memory module).
Memory-slot or memory-module is probabl
Hi,
On Wed, Dec 19, 2012 at 08:27:36AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > - multiple memory buses can be registered. Memory buses of the real
> > hw/chipset
> > or a paravirtual memory bus can be added.
>
> IIRC q35 supports memory hotplug natively (picked up in some
> discussion). Is
Hi,
> - multiple memory buses can be registered. Memory buses of the real hw/chipset
> or a paravirtual memory bus can be added.
IIRC q35 supports memory hotplug natively (picked up in some
discussion). Is that correct?
What does the code emulate? It doesn't look like it emulates q35 memor
HI,
One stupid question, 'dimm' presents one guest memory, then why it is
called as "dimm"? what is its full name?
On Tue, Dec 18, 2012 at 8:41 PM, Vasilis Liaskovitis
wrote:
> This is v4 of the ACPI memory hotplug functionality. Only x86_64 target is
> supported (both i440fx and q35). There are
This is v4 of the ACPI memory hotplug functionality. Only x86_64 target is
supported (both i440fx and q35). There are still several issues, but it's
been a while since v3 and I wanted to get some more feedback on the current
state of the patchseries.
Overview:
Dimm device layout is modeled with a
26 matches
Mail list logo
