On Wed, Sep 28, 2011 at 3:02 AM, Gabe Black gbl...@eecs.umich.edu wrote:
Changing the scripts may or may not be a big deal. Our scripts are not
very modular or flexible, so it's hard to say.
Yes, our scripts are definitely nowhere near as modular as they should be,
which indicates that
Sounds basically like the right direction. I suggest using a tuple rather
than a list if you intend it to be read-only, and also to consider having a
class you can instantiate to represent the list members if they get
complicated. I know there are other places where I've done if it's a
scalar,
Quoting Steve Reinhardt ste...@gmail.com:
On Wed, Sep 28, 2011 at 3:09 AM, Gabe Black gbl...@eecs.umich.edu wrote:
A PageTable object is an example of an address space. A guest
page table in memory is an address space. Because we have two,
incompatible abstractions for essentially the same
One thing I don't agree with is that they should be associated with
the system object. It doesn't need to know how the PCI space is
allocated or be able to send interrupts to the CPU through the
chipset's IO controller. Devices do, but moving radially outwards from
the CPU they are (for
On Fri, Sep 30, 2011 at 9:18 PM, Gabriel Michael Black
gbl...@eecs.umich.edu wrote:
One thing I don't agree with is that they should be associated with the
system object. It doesn't need to know how the PCI space is allocated or be
able to send interrupts to the CPU through the chipset's IO
On Fri, Sep 30, 2011 at 9:12 PM, Gabriel Michael Black
gbl...@eecs.umich.edu wrote:
That's why a Kernel and a Process are both workloads... They *are*
basically the same thing, just in different contexts, which is what I'm
getting at.
Yea, I'm not disagreeing with that.
And we do need a
