[lkml]   [2011]   [Jun]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver
    On Friday 10 June 2011, Chris Metcalf wrote:
    > This still leaves open the question of what really should go in this new
    > directory. Is it just for drivers that manage/control the hypervisor? Or
    > is it also for drivers that just use the hypervisor to do I/O of some kind,
    > but aren't related to any other "family" of drivers, i.e., a driver that
    > would have been dumped in drivers/char or drivers/misc in the old days?
    > My specific interest at the moment is the proposed tile-srom.c driver
    > (, which uses a simple
    > hypervisor read/write API to access the portion of the SPI ROM used to hold
    > the boot stream for a TILE processor.

    I'd still put that driver in drivers/char for now, because it already contains
    similar drivers. We can probaby group them in a subdirectory of drivers/char
    at some point or move them out to a new directory.

    For your raw hcall passthrough driver, that would be something that should
    go into drivers/virt/ IMHO.


     \ /
      Last update: 2011-06-10 17:39    [W:0.021 / U:6.804 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site