> On March 18, 2011, 1:54 p.m., Gabe Black wrote: > > It seems like we should be able to emulate the access system call fairly > > easily. It basically just checks if a file can be accessed in certain ways, > > I think. We could do that on the real file descriptor, rearrange the result > > if necessary, and pass it back. The other syscall changes here look ok. > > Lisa Hsu wrote: > Would you object to committing/pushing as is and emulating access() if it > ever becomes necessary in the future? It's not something I'm going to commit > to doing, and I wouldn't want everything else to get held up because of it. > > Gabe Black wrote: > How is access() being used right now? It would be dangerous to assume > just because it didn't seem to cause a problem by ignoring it that it's > actually safe to do so, and it must be used by something or that line > wouldn't be necessary. I would rather we did this safely than expediently. > This change, or at least that line, should be independent of any other change > as far as I've seen and shouldn't hold anything else up. > > Ali Saidi wrote: > well... all it seems like you would need to do is return 0 when it's > called. That means you can access the file and I doubt we would ever have a > case where you couldn't. > > Gabe Black wrote: > That sounds about right, and that should be really easy to implement. We > should make sure we put a comment in there explaining why we're always > returning 0. > > Ali Saidi wrote: > prod
Actually printing a warning and returning zero is exactly what ignoreFunc does, so I don't see much reason to create a special implementation for access() that does the same thing. - Steve ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/588/#review980 ----------------------------------------------------------- On March 17, 2011, 4:05 p.m., Lisa Hsu wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/588/ > ----------------------------------------------------------- > > (Updated March 17, 2011, 4:05 p.m.) > > > Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and > Nathan Binkert. > > > Description > ------- > > X86: SE syscalls: patch from Vince Weaver for review > > > Diffs > ----- > > src/arch/x86/linux/syscalls.cc 2e269d6fb3e6 > > Diff: http://reviews.gem5.org/r/588/diff/diff > > > Testing > ------- > > I've done minimal testing on these, i.e. I've pushed them to a clean tree and > run X86 SPEC2k6 binaries on them, some of which didn't work prior to the > patches but now do. Others remain broken. Vince, however, has done lots of > testing and basically needed these to run SPEC2K workloads to completion for > his thesis. In other words, I bet these patches are good, but not complete > for the purposes of running SPEC2k6. > > > Thanks, > > Lisa Hsu > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
