Hi,
On Thu, Oct 18, 2012 at 02:33:02PM +0200, Avi Kivity wrote:
On 10/18/2012 11:27 AM, Vasilis Liaskovitis wrote:
On Wed, Oct 17, 2012 at 12:03:51PM +0200, Avi Kivity wrote:
On 10/17/2012 11:19 AM, Vasilis Liaskovitis wrote:
I don't think so, but probably there's a limit of DIMMs that
On 10/19/2012 07:48 PM, Blue Swirl wrote:
DIMMs would be allowed to be hotplugged in the generic mem-controller
scheme only
(unless it makes sense to allow hotplug in the remaining pmc DRBs and
start using the generic scheme once we run out of emulated DRBs)
440fx seems a lost cause, so
On Thu, Oct 18, 2012 at 12:33 PM, Avi Kivity a...@redhat.com wrote:
On 10/18/2012 11:27 AM, Vasilis Liaskovitis wrote:
On Wed, Oct 17, 2012 at 12:03:51PM +0200, Avi Kivity wrote:
On 10/17/2012 11:19 AM, Vasilis Liaskovitis wrote:
I don't think so, but probably there's a limit of DIMMs that
On Wed, Oct 17, 2012 at 12:03:51PM +0200, Avi Kivity wrote:
On 10/17/2012 11:19 AM, Vasilis Liaskovitis wrote:
I don't think so, but probably there's a limit of DIMMs that real
controllers have, something like 8 max.
In the case of i440fx specifically, do you mean that we should model
On 10/18/2012 11:27 AM, Vasilis Liaskovitis wrote:
On Wed, Oct 17, 2012 at 12:03:51PM +0200, Avi Kivity wrote:
On 10/17/2012 11:19 AM, Vasilis Liaskovitis wrote:
I don't think so, but probably there's a limit of DIMMs that real
controllers have, something like 8 max.
In the case of
On Sat, Oct 13, 2012 at 08:57:19AM +, Blue Swirl wrote:
On Tue, Oct 9, 2012 at 5:04 PM, Vasilis Liaskovitis
vasilis.liaskovi...@profitbricks.com wrote:
snip
Maybe even the dimmbus device shouldn't exist by itself after all, or
it should be pretty much invisible to users. On real HW,
On 10/17/2012 11:19 AM, Vasilis Liaskovitis wrote:
I don't think so, but probably there's a limit of DIMMs that real
controllers have, something like 8 max.
In the case of i440fx specifically, do you mean that we should model the DRB
(Dram row boundary registers in section 3.2.19 of the
On Tue, Oct 9, 2012 at 5:04 PM, Vasilis Liaskovitis
vasilis.liaskovi...@profitbricks.com wrote:
Hi,
sorry for the delayed answer.
On Sat, Sep 29, 2012 at 11:13:04AM +, Blue Swirl wrote:
The -dimm option is supposed to specify the dimm/memory layout, and not
create
any devices.
Hi,
sorry for the delayed answer.
On Sat, Sep 29, 2012 at 11:13:04AM +, Blue Swirl wrote:
The -dimm option is supposed to specify the dimm/memory layout, and not
create
any devices.
If we don't want this new option, I have a question:
A -device/device_add means we create a
On Mon, Sep 24, 2012 at 10:42 AM, Vasilis Liaskovitis
vasilis.liaskovi...@profitbricks.com wrote:
On Sat, Sep 22, 2012 at 01:46:57PM +, Blue Swirl wrote:
On Fri, Sep 21, 2012 at 11:17 AM, Vasilis Liaskovitis
vasilis.liaskovi...@profitbricks.com wrote:
Example:
-dimm
On Sat, Sep 22, 2012 at 01:46:57PM +, Blue Swirl wrote:
On Fri, Sep 21, 2012 at 11:17 AM, Vasilis Liaskovitis
vasilis.liaskovi...@profitbricks.com wrote:
Example:
-dimm id=dimm0,size=512M,node=0,populated=off
There should not be a need to introduce a new top level option,
instead you
On Fri, Sep 21, 2012 at 11:17 AM, Vasilis Liaskovitis
vasilis.liaskovi...@profitbricks.com wrote:
Example:
-dimm id=dimm0,size=512M,node=0,populated=off
There should not be a need to introduce a new top level option,
instead you should just use -device, like
-device
Example:
-dimm id=dimm0,size=512M,node=0,populated=off
will define a 512M memory slot belonging to numa node 0.
When populated=on, a DimmDevice is created and hot-plugged at system startup.
Signed-off-by: Vasilis Liaskovitis vasilis.liaskovi...@profitbricks.com
---
hw/Makefile.objs |2 +-
13 matches
Mail list logo
